Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s AMD XDNA accelerator driver can schedule work while a hardware context is being freed. This may cause use-after-free memory corruption and system crashes. The supplied CVSS assessment indicates potential loss of confidentiality, integrity, and availability, but the attack requires local, low-privileged access.
Executive priority
Treat this as a high-priority, targeted kernel update for systems actively using AMD XDNA acceleration. Local access requirements reduce broad Internet-facing urgency, but potential memory corruption and complete confidentiality, integrity, and availability impact justify prompt remediation where shared or untrusted users can access the accelerator.
Technical view
A race in accel/amdxdna permits jobs to run across aie2_release_resource(), allowing access to released hardware-context memory. The fix pauses scheduling during resource release and makes aie2_sched_job_run() verify that the context remains active. CVSS 3.1 is 7.8: local, low complexity, low privileges, no user interaction, with high impact.
Likely exposure
Exposure is limited to affected Linux builds using the AMD XDNA acceleration driver, particularly where low-privileged users can submit accelerator jobs. Internet reachability alone does not create the stated attack path. The bundle’s version and commit metadata is insufficient to determine exact distribution package exposure or backport status.
Exploitation context
The CVSS vector describes a local, low-privilege attack requiring no user interaction. The supplied record is not listed in KEV and provides no evidence of active exploitation or a public weaponized exploit. Confirmed outcomes include use-after-free and crashes; broader security impact is reflected by the supplied CVSS assessment.
Researcher notes
The defect is a resource-lifecycle race between job scheduling and hardware-context teardown. Analysis should focus on reachability of AMD XDNA job submission by local users and distribution-specific backports. The supplied sources establish the race and fix design, but do not establish exploit reliability, affected hardware breadth, or real-world exploitation.
Mitigation direction
- Install a vendor kernel update containing the referenced stable fix for the deployed kernel branch.
- Prioritize affected systems offering AMD XDNA acceleration to untrusted or lower-privileged local users.
- If updates are delayed, consult vendor guidance for safe restrictions on affected accelerator access.
- Avoid assuming upstream version numbers directly match distribution packages with backported fixes.
Validation and detection
- Inventory kernel packages and determine whether the accel/amdxdna driver is present and used.
- Map each distribution kernel to vendor advisories or the referenced fixed commits.
- Confirm the installed update contains scheduling suspension and active-context validation changes.
- Regression-test AMD XDNA workloads and hardware-context teardown after updating.
- Monitor affected hosts for driver crashes or use-after-free reports during remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-45980 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/b79d31dce49b50c79620389b3639280802a86960CVE reference, Linux
- https://git.kernel.org/stable/c/688c3ff079b10e4600f040944430d3d4ff448a15CVE reference, Linux
- https://git.kernel.org/stable/c/f1370241fe8045702bc9d0812b996791f0500f1bCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.