LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47042: drm/amd/display: Free local data after use

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Free local data after use Fixes the following memory leak in dc_link_construct(): unreferenced object 0xffffa03e81471400 (size 1024): comm "amd_module_load", pid 2486, jiffies 4294946026 (age 10.544s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000000bdf5c4a>] kmem_cache_alloc_trace+0x30a/0x4a0 [<00000000e7c59f0e>] link_create+0xce/0xac0 [amdgpu] [<000000002fb6c072>] dc_create+0x370/0x720 [amdgpu] [<000000000094d1f3>] amdgpu_dm_init+0x18e/0x17a0 [amdgpu] [<00000000bec048fd>] dm_hw_init+0x12/0x20 [amdgpu] [<00000000a2bb7cf6>] amdgpu_device_init+0x1463/0x1e60 [amdgpu] [<0000000032d3bb13>] amdgpu_driver_load_kms+0x5b/0x330 [amdgpu] [<00000000a27834f9>] amdgpu_pci_probe+0x192/0x280 [amdgpu] [<00000000fec7d291>] local_pci_probe+0x47/0xa0 [<0000000055dbbfa7>] pci_device_probe+0xe3/0x180 [<00000000815da970>] really_probe+0x1c4/0x4e0 [<00000000b4b6974b>] driver_probe_device+0x62/0x150 [<000000000f9ecc61>] device_driver_attach+0x58/0x60 [<000000000f65c843>] __driver_attach+0xd6/0x150 [<000000002f5e3683>] bus_for_each_dev+0x6a/0xc0 [<00000000a1cfc897>] driver_attach+0x1e/0x20

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-47042 is a Linux kernel AMD display driver memory leak. The source describes leaked memory during AMDGPU module loading, not a remote compromise path. Business urgency is mainly for systems running affected Linux kernels with AMD graphics, especially fleets where repeated driver initialization could create stability risk.

Executive priority

Treat this as routine kernel maintenance unless affected AMDGPU systems are stability-sensitive. There is no supplied evidence of exploitation or remote compromise, but unpatched kernel driver leaks can still create operational reliability risk.

Technical view

The issue is in Linux kernel drm/amd/display, where dc_link_construct/link_create allocated local data that was not freed. The provided backtrace shows the leak during amd_module_load through amdgpu initialization. Stable kernel commits are referenced as the resolution. No CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the AMDGPU display stack. The bundle lists Linux kernel 5.12-related affected version data and stable fixes, but distribution backport status must be verified per vendor kernel package.

Exploitation context

The bundle does not report active exploitation, KEV listing, public exploit use, or a remote attack vector. Evidence supports a memory leak during local AMDGPU driver initialization rather than an externally reachable vulnerability.

Researcher notes

The source evidence is narrow: a kernel memory leak fix with a diagnostic backtrace and two stable commit references. Version metadata is incomplete for distribution kernels, so validation should focus on vendor package status and whether AMDGPU display code is present.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported AMDGPU fixes.
  • Prioritize systems with AMD graphics and affected 5.12-era kernels.
  • Monitor vendor guidance if exact package mapping is unclear.

Validation and detection

  • Inventory Linux kernel versions and AMDGPU usage across assets.
  • Map installed kernels to distribution security advisories or stable commits.
  • Review kernel logs for AMDGPU initialization issues or leak reports.
  • Confirm patched hosts no longer match affected kernel package ranges.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-47042 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3a00c04212d1cfe1426338b78f4ead623508c874, 3a00c04212d1cfe1426338b78f4ead623508c874unaffected
LinuxLinux5.12, 0, 5.12.4, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.