LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71308: accel/amdxdna: Fix potential NULL pointer dereference in context cleanup

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Fix potential NULL pointer dereference in context cleanup aie_destroy_context() is invoked during error handling in aie2_create_context(). However, aie_destroy_context() assumes that the context's mailbox channel pointer is non-NULL. If mailbox channel creation fails, the pointer remains NULL and calling aie_destroy_context() can lead to a NULL pointer dereference. In aie2_create_context(), replace aie_destroy_context() with a function which request firmware to remove the context created previously.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the AMD XDNA accelerator driver cleanup path. Under a specific failure condition, the kernel can dereference a missing mailbox channel pointer and crash. The sources do not provide severity, CVSS, exploitability, or evidence of active exploitation.

Executive priority

Track and patch through normal kernel maintenance unless AMD XDNA accelerator workloads are business-critical. Escalate if vendors assign higher severity or confirm reachable denial-of-service conditions.

Technical view

In accel/amdxdna, aie2_create_context() error handling can call aie_destroy_context() after mailbox channel creation fails. aie_destroy_context() assumes the channel pointer exists, causing a potential NULL pointer dereference. The fix changes cleanup to request firmware removal of the previously created context.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds that include and use the accel/amdxdna driver. The bundle lists Linux kernel versions and stable commits, but does not identify distributions, appliances, or cloud images.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, required privileges, or remote reachability. KEV is false. Treat this as a kernel stability and potential denial-of-service concern until vendor advisories clarify impact.

Researcher notes

Evidence is limited to the CVE description and two Linux stable commit references. Key unknowns are trigger requirements, privilege boundary, affected distribution kernels, and practical impact beyond NULL pointer dereference during context creation error handling.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for affected package versions.
  • Prioritize systems using AMD XDNA accelerator support.
  • If unable to patch, request vendor-supported workarounds.
  • Do not assume a workaround exists from the provided sources.

Validation and detection

  • Inventory running Linux kernel versions across affected systems.
  • Check whether accel/amdxdna support is present or loaded.
  • Compare kernel package changelogs against the referenced stable commits.
  • Review vendor advisories for CVE-2025-71308 applicability.
  • Monitor kernel logs for related amdxdna context cleanup crashes.
Prepared
Confidence
medium
Sources
4

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-71308 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
3Source 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
LinuxLinuxbe462c97b7dfd24999babe39cce3de224ebe1f80, be462c97b7dfd24999babe39cce3de224ebe1f80unaffected
LinuxLinux6.14, 0, 6.19.4, 7.0affected
Weakness

CWE details

No CWE listed

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