LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21784: drm/amdgpu: bail out when failed to load fw in psp_init_cap_microcode()

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: bail out when failed to load fw in psp_init_cap_microcode() In function psp_init_cap_microcode(), it should bail out when failed to load firmware, otherwise it may cause invalid memory access.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-21784 is a Linux kernel amdgpu driver flaw. If AMD GPU PSP capability firmware fails to load, the driver may continue instead of stopping, leading to invalid memory access. The business impact is most likely system instability or crashes on affected Linux systems using AMD GPU support.

Executive priority

Treat as a routine-to-priority kernel maintenance item for AMD GPU environments. Escalate if affected systems support critical workloads, GPU compute, or high-availability desktops, because kernel memory faults can disrupt operations.

Technical view

The issue is in drm/amdgpu psp_init_cap_microcode(). The kernel fix changes behavior to bail out when firmware loading fails, preventing later invalid memory access. Public sources do not provide CVSS, CWE, exploitability details, or a precise distro-level package matrix.

Likely exposure

Exposure appears limited to Linux systems with the affected amdgpu kernel code path, especially systems using AMD GPUs where PSP capability firmware loading can fail. The CVE record lists Linux kernel versions and stable commits, but distro-specific affected package names are not provided.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. The public description suggests a reliability and memory-safety issue triggered by firmware load failure, not a documented remote attack path.

Researcher notes

Evidence is sparse. The root cause and fix are clear from the kernel description, but impact boundaries, privilege requirements, and exploitability are not documented in the supplied sources. Avoid assuming remote exploitability or privilege escalation without further vendor analysis.

Mitigation direction

  • Upgrade to a kernel containing the referenced stable fixes.
  • Check your Linux distribution security advisories for backported kernel updates.
  • Prioritize AMD GPU Linux hosts, workstations, and GPU compute nodes.
  • If patching is delayed, monitor for amdgpu firmware load failures and kernel instability.

Validation and detection

  • Inventory Linux hosts using the amdgpu driver.
  • Compare running kernel builds against vendor advisories and referenced stable commits.
  • Review boot and kernel logs for amdgpu PSP firmware load failures.
  • Confirm patched kernels include the psp_init_cap_microcode bailout fix.
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-2025-21784 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
5Source 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
LinuxLinux07dbfc6b102e25087ec345ef2c2eae21c9856f17, 07dbfc6b102e25087ec345ef2c2eae21c9856f17, 07dbfc6b102e25087ec345ef2c2eae21c9856f17, 07dbfc6b102e25087ec345ef2c2eae21c9856f17unaffected
LinuxLinux6.3, 0, 6.6.79, 6.12.16, 6.13.4, 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.