CVE-2026-45931

Analyzed Analyzed - Analysis Complete

Memory Corruption in Linux Kernel AMDXDNA Driver

Publication date: 2026-05-27

Last updated on: 2026-06-25

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-25

Generated

2026-07-07

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-45931

EUVD

EUVD-2026-32215

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 6.19.4 (exc)
linux	linux_kernel	From 6.14 (inc) to 6.18.14 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel within the accel/amdxdna component. It occurs because some tests cause a crash in the function iommu_sva_unbind_device() by accessing iommu_mm after the associated memory management (mm) structure has already been freed.

The issue is fixed by explicitly holding a reference to the mm structure after the device is successfully bound, and only releasing it after the device is unbound. This ensures that the mm structure remains valid throughout the entire lifetime of the SVA (Shared Virtual Addressing) bind and unbind process.

Impact Analysis

This vulnerability can cause crashes in the Linux kernel when the iommu_sva_unbind_device() function accesses memory management structures that have already been freed. Such crashes can lead to system instability, potential denial of service, or unexpected behavior in systems using the affected kernel component.

Hi! I’m here to help you understand CVE-2026-45931. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70