LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47431: drm/amdgpu: fix gart.bo pin_count leak

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix gart.bo pin_count leak gmc_v{9,10}_0_gart_disable() isn't called matched with correspoding gart_enbale function in SRIOV case. This will lead to gart.bo pin_count leak on driver unload.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects AMDGPU SR-IOV environments. A driver unload path can leak a GART buffer object pin count, creating an operational reliability risk rather than a clearly documented data theft or remote compromise scenario. The source bundle provides no CVSS score or confirmed exploitation.

Executive priority

Treat as a targeted kernel maintenance item for AMDGPU SR-IOV infrastructure. It does not justify emergency response from the provided evidence, but affected virtualization or GPU workloads should be patched through normal kernel update processes.

Technical view

The resolved kernel bug is in drm/amdgpu: gmc_v9/gmc_v10 GART disable handling is not paired correctly with the corresponding enable path in SR-IOV cases, causing gart.bo pin_count leakage during driver unload. Stable kernel commits are referenced as fixes.

Likely exposure

Exposure is most likely on Linux systems using AMDGPU with SR-IOV and kernel versions or downstream builds containing the affected amdgpu code. Systems without AMDGPU SR-IOV use are less likely to encounter the described path.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. No exploit mechanism is described. The evidence points to a driver lifecycle resource leak during unload, not a documented remote attack path.

Researcher notes

Evidence is limited to the CVE record and stable kernel commits. No CVSS, CWE, exploitability analysis, or downstream distro status is included. Further assessment should focus on whether local kernels include the affected amdgpu SR-IOV path.

Mitigation direction

  • Apply vendor or distro kernel updates containing the referenced stable amdgpu fix.
  • Check Linux distribution advisories for CVE-2021-47431 package status.
  • Prioritize AMDGPU SR-IOV hosts over general Linux fleet patching.
  • Avoid inventing workarounds; follow kernel or distro maintainer guidance.

Validation and detection

  • Inventory Linux hosts using AMDGPU and SR-IOV.
  • Compare running kernel packages against distro CVE-2021-47431 advisories.
  • Confirm kernel changelogs include the gart.bo pin_count leak fix.
  • After updating, verify the host runs the updated kernel build.
Prepared
Confidence
medium
Sources
6

Public sources used

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-47431 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
5Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 5.4.154, 5.10.74, 5.14.13, 5.15affected
Weakness

CWE details

No CWE listed

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