LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47142: drm/amdgpu: Fix a use-after-free

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix a use-after-free looks like we forget to set ttm->sg to NULL. Hit panic below [ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI [ 1235.989074] Call Trace: [ 1235.991751] sg_free_table+0x17/0x20 [ 1235.995667] amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu] [ 1236.002288] amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu] [ 1236.008464] ttm_tt_destroy+0x1e/0x30 [ttm] [ 1236.013066] ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm] [ 1236.018783] ttm_bo_release+0x262/0xa50 [ttm] [ 1236.023547] ttm_bo_put+0x82/0xd0 [ttm] [ 1236.027766] amdgpu_bo_unref+0x26/0x50 [amdgpu] [ 1236.032809] amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu] [ 1236.040400] kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu] [ 1236.046912] kfd_ioctl+0x463/0x690 [amdgpu]

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel AMD GPU driver bug that can crash a system when the affected memory cleanup path is hit. The provided sources describe a use-after-free in amdgpu, with a kernel panic trace. Business risk is mainly availability for Linux systems using affected AMD GPU driver code.

Executive priority

Treat as a targeted availability risk for AMD GPU Linux fleets. Prioritize patching where GPU workloads support production services, shared workstations, or research compute. Broader urgency is uncertain because the bundle lacks CVSS, exploit evidence, and full impact details.

Technical view

CVE-2021-47142 is a use-after-free in Linux drm/amdgpu. The source says ttm->sg was not set to NULL, allowing sg_free_table to operate on stale memory during amdgpu TTM backend cleanup. The trace occurs through KFD GPU memory allocation and ends in a general protection fault.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with AMD GPU support through amdgpu/KFD. Systems without AMD GPUs or without the affected driver path are less likely exposed. The affected version data in the bundle is limited and should be validated against distro kernel packages.

Exploitation context

The bundle does not report active exploitation, and kev is false. The evidence shows a crash/panic condition from a kernel driver use-after-free. The call trace suggests a local GPU memory allocation path, but the sources do not provide a complete exploitability assessment.

Researcher notes

Focus review on amdgpu TTM backend unbind/destroy behavior and whether ttm->sg is cleared after freeing. The public record includes multiple stable commit references but does not include CWE, CVSS, or exploit status. Validate exact affected ranges through kernel or distro metadata.

Mitigation direction

  • Apply vendor kernel updates containing the referenced amdgpu stable fixes.
  • Check Linux distribution advisories for the matching backported kernel package.
  • Prioritize systems using AMD GPUs for compute, desktop, or graphics workloads.
  • Avoid inventing compensating controls until vendor guidance is reviewed.

Validation and detection

  • Inventory Linux hosts with AMD GPUs and the amdgpu driver enabled.
  • Compare running kernel packages against vendor-fixed versions or referenced stable commits.
  • Review crash logs for amdgpu, KFD, sg_free_table, or general protection faults.
  • Confirm change control includes rebooting into the fixed kernel.
Prepared
Confidence
medium
Sources
10

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-47142 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
9Source 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
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 4.4.271, 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42, 5.12.9, 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.