CVE-2026-45931: accel/amdxdna: Hold mm structure across iommu_sva_unbind_device()
In the Linux kernel, the following vulnerability has been resolved:
accel/amdxdna: Hold mm structure across iommu_sva_unbind_device()
Some tests trigger a crash in iommu_sva_unbind_device() due to
accessing iommu_mm after the associated mm structure has been
freed.
Fix this by taking an explicit reference to the mm structure
after successfully binding the device, and releasing it only
after the device is unbound. This ensures the mm remains valid
for the entire SVA bind/unbind lifetime.
Security readout for executives and security teams
Plain-English summary
A Linux AMD XDNA accelerator driver flaw can access memory-management data after it has been freed during device unbinding, causing a kernel crash. The supplied CVSS score is 7.8 because a local, low-privileged attacker may potentially affect confidentiality, integrity, and availability, although the sources only directly document test-triggered crashes.
Executive priority
Treat as a high-priority kernel update for systems using AMD XDNA acceleration, especially multi-user or shared-compute hosts. Other Linux systems are less likely to reach the vulnerable path, but version and driver exposure should be verified promptly rather than assumed.
Technical view
The accel/amdxdna driver does not retain the process mm structure for the complete IOMMU Shared Virtual Addressing bind/unbind lifetime. iommu_sva_unbind_device() can therefore access iommu_mm after its associated mm is freed. The kernel fix takes an explicit mm reference after binding and releases it after unbinding.
Likely exposure
Exposure appears limited to affected Linux kernels using the AMD XDNA accelerator driver and IOMMU SVA functionality. The bundle lists versions including 6.14, 6.18.14, 6.19.4, and 7.0, but does not provide sufficiently clear range semantics; confirm status with the kernel or distribution vendor.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction. The supplied record is not in KEV, and no cited source reports active exploitation or a public exploit. Test-triggered kernel crashes are documented; broader confidentiality or integrity impact is scored but not demonstrated in the supplied evidence.
Researcher notes
This is a lifetime-management defect resembling use-after-free behavior, but the CVE record supplies no CWE. Evidence establishes stale mm access and crashes during testing. It does not establish reliable privilege escalation, information disclosure, active exploitation, or exact affected-version intervals. The referenced stable commits are the strongest basis for fix verification.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fix.
Confirm fixed-package availability and affected version boundaries with your Linux distribution vendor.
Prioritize systems exposing AMD XDNA acceleration to untrusted or low-privileged local users.
Restrict unnecessary local access until affected systems are updated.
Validation and detection
Inventory kernel versions and distribution package revisions on systems with AMD XDNA hardware.
Determine whether the accel/amdxdna driver and IOMMU SVA path are active.
Compare deployed kernel sources or vendor advisories against the three referenced stable commits.
Review kernel logs for crashes involving iommu_sva_unbind_device or AMD XDNA teardown.
After updating, verify the vendor package includes the mm-reference lifetime fix.
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-2026-45931 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We 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.