Linux kernel amdxdna: use-after-free on the IOMMU domain when the accelerator device is removed

CVE-2026-80608NVIDIA / GPU stackcurated

Impact

In force_iova mode the amdxdna driver frees xdna->domain inside amdxdna_remove(), but a GEM buffer object freed after device removal can still dereference that pointer, giving a use-after-free on a kernel IOMMU domain structure. The scored vector is local, low-privilege, with a scope change and high confidentiality, integrity and availability impact, which is consistent with corruption of kernel memory reachable from an unprivileged holder of the accelerator device node. Exposure is limited to hosts that actually have an AMD XDNA NPU bound to this driver - it is a client/workstation accelerator part, not something present on server GPU nodes - so most fleets will find the driver absent. Where it is present, the race needs device removal (hot-unplug, driver unbind, or a teardown path) to run concurrently with buffer teardown.

Who can reach it

Local user with an open handle to the amdxdna accelerator device, racing a device removal or driver unbind. No remote or network path; no unauthenticated path.

What to do

Take the stable-kernel fix that converts the domain free into a DRM managed release action (commits 65e7e2b8d71b and b4a0500fdf6e) via a distribution kernel update, then reboot the affected host. On fleets with no AMD XDNA hardware the driver is not loaded and no action is required; blacklisting amdxdna is a valid stopgap where the NPU is unused. The record names no fixed release numbers, only the stable commits.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-80608 https://git.kernel.org/stable/c/65e7e2b8d71b418439ebc68e80ed3e5a325375d6 https://git.kernel.org/stable/c/b4a0500fdf6e61a6c5f92ff2e61bc91578075803

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.