PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-45931 Linux CVE debrief

A use-after-free vulnerability in the Linux kernel's AMD XDNA AI accelerator driver (accel/amdxdna) could allow local attackers to trigger system crashes. The flaw occurs when the IOMMU Shared Virtual Address (SVA) unbind operation accesses a memory management (mm) structure that has already been freed. The fix ensures the mm structure reference is held for the entire SVA bind/unbind lifetime by explicitly taking a reference after successful device binding and releasing it only after unbinding completes.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-27
Original CVE updated
2026-06-25
Advisory published
2026-05-27
Advisory updated
2026-06-25

Who should care

Organizations running Linux systems with AMD XDNA AI accelerator hardware, particularly those in multi-user environments where local access cannot be fully restricted. Cloud providers and HPC facilities offering AMD XDNA-based instances should prioritize kernel updates.

Technical summary

The accel/amdxdna driver in the Linux kernel contains a use-after-free vulnerability in its IOMMU SVA (Shared Virtual Address) handling code. When iommu_sva_unbind_device() is called, it may access the iommu_mm structure after the associated mm (memory management) structure has been freed, leading to a kernel crash. The root cause is improper lifetime management of the mm structure reference across the SVA bind/unbind operations. The resolution adds explicit reference counting: mmget() is called after successful device binding, and mmput() is called only after the device is fully unbound, ensuring the mm structure remains valid throughout the entire SVA lifecycle. This vulnerability affects systems with AMD XDNA AI accelerators and requires local access to trigger.

Defensive priority

medium

Recommended defensive actions

  • Apply kernel updates containing the referenced stable tree commits when available from your Linux distribution
  • Monitor vendor security advisories for kernel package updates addressing this vulnerability
  • If running systems with AMD XDNA AI accelerators, prioritize patching to prevent potential local denial-of-service conditions
  • Review system logs for any prior crashes in iommu_sva_unbind_device() that may indicate exploitation attempts
  • Consider restricting local access to systems with AMD XDNA hardware until patches can be applied

Evidence notes

The vulnerability description indicates this was discovered through testing that triggered crashes in iommu_sva_unbind_device(). The fix involves proper reference counting of the mm structure across the SVA bind/unbind lifecycle. Three kernel stable tree commits are referenced, suggesting backports to multiple kernel versions.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-45931 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-45931

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-45931 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45931

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a9162439ad792afcddc04718408ec1380b7a5f63

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/f31ccf6278132a35a652fe5eeac3941e1e912398

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/f6b4c1d98a7b8040d4d02e89425b3942016a2c2c

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.