LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21987: drm/amdgpu: init return value in amdgpu_ttm_clear_buffer

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: init return value in amdgpu_ttm_clear_buffer Otherwise an uninitialized value can be returned if amdgpu_res_cleared returns true for all regions. Possibly closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3812 (cherry picked from commit 7c62aacc3b452f73a1284198c81551035fac6d71)

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel amdgpu driver bug where a function could return an uninitialized value in a specific buffer-clearing path. The business risk is unclear because the public record provides no CVSS score, CWE, or exploitation evidence. Treat affected AMD GPU Linux systems as needing routine kernel remediation, with urgency adjusted by asset criticality.

Executive priority

Set priority as medium operational hygiene unless asset criticality is high. There is no cited exploitation evidence, but kernel flaws can be difficult to assess and should not remain unpatched on production systems using the affected driver.

Technical view

The issue is in drm/amdgpu, specifically amdgpu_ttm_clear_buffer. If amdgpu_res_cleared returns true for all regions, the function could return an uninitialized value. The kernel record says the vulnerability has been resolved and points to stable commits that initialize the return value.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the amdgpu driver path present. The source bundle lists affected Linux version metadata including 6.10, 6.12.18, 6.13.6, and 6.14, but exact downstream distro package impact must be confirmed with vendor advisories.

Exploitation context

The source bundle does not show active exploitation, proof-of-concept availability, or KEV listing. It describes a resolved kernel bug and references stable kernel commits. There is insufficient public evidence here to characterize exploitability beyond the affected driver logic.

Researcher notes

The public data is sparse: no CVSS, CWE, exploit discussion, or detailed impact statement is included. Analysis should focus on kernel provenance, affected branch mapping, whether amdgpu_ttm_clear_buffer is reachable in local workloads, and confirmation of the stable fix in downstream kernels.

Mitigation direction

  • Update affected Linux kernels through the normal distribution or vendor kernel update channel.
  • Confirm the update includes one of the referenced stable kernel fixes.
  • Prioritize systems using AMD GPUs or loading the amdgpu driver.
  • Monitor Linux distribution advisories for backported fixed package versions.
  • Avoid claiming remediation complete until the running kernel is verified.

Validation and detection

  • Inventory Linux kernel versions across systems that may use AMD GPU hardware.
  • Check whether the amdgpu driver is present or loaded on relevant hosts.
  • Compare installed kernel packages against vendor advisories for CVE-2025-21987.
  • Verify the deployed kernel includes the referenced upstream stable fix.
  • Document unsupported or custom kernels for separate remediation review.
Prepared
Confidence
medium
Sources
5

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-2025-21987 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
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa68c7eaa7a8ffdec9287ba1561a668d674c20a13, a68c7eaa7a8ffdec9287ba1561a668d674c20a13, a68c7eaa7a8ffdec9287ba1561a668d674c20a13unaffected
LinuxLinux6.10, 0, 6.12.18, 6.13.6, 6.14affected
Weakness

CWE details

No CWE listed

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