Look up another CVE · open CVE-2026-80608 in the interactive tracker
CVE-2026-80608
accel/amdxdna: Fix iommu domain lifetime race during device removal
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/accel. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80608 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
When force_iova mode is enabled, amdxdna_remove() frees xdna->domain. If amdxdna_gem_obj_free() is called after device removal, it may attempt to access xdna->domain, resulting in a use-after-free. Fix the race by adding freeing xdna->domain as a managed release action, so its lifetime is managed by DRM and remains valid until all managed resources are released.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/accel/amdxdna/amdxdna_iommu.c
- What this is
- AMD XDNA DRIVERMAINTAINERS section matched on drivers/accel/amdxdna/ · dri-devel@lists.freedesktop.org · Supported
- Kernel module
- amdxdna
Check it on the machine
grep -wE 'CONFIG_DRM_ACCEL|CONFIG_DRM_ACCEL_AMDXDNA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w amdxdnaPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_DRM_ACCEL, CONFIG_DRM_ACCEL_AMDXDNA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/accel
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.1 | 7.1.5 | 65e7e2b8d71b |
| 7.1 | 7.2 | b4a0500fdf6e |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The UAF is reached via local /dev/accel/accel* syscalls (open, DRM_IOCTL_AMDXDNA_CREATE_BO, close) that call amdxdna_gem_obj_free()→amdxdna_dma_unmap_bo(); there is no network, adjacent-radio, or physical-bus entry to this AMD XDNA NPU driver path.
- AC:LAttack complexity, low
- This is a lifetime race between amdxdna_remove() freeing xdna->domain and concurrent GEM teardown; an attacker controls both sides with threads holding DMA-mapped BOs while triggering driver unbind/rmmod or rapid create/destroy ioctls, reliably hitting the post-removal amdxdna_dma_unmap_bo() UAF window.
- PR:LPrivileges required, low
- Vulnerable ioctls use DRM_IOCTL_DEF_DRV flags 0 (no DRM_ROOT_ONLY/DRM_AUTH); any local user permitted to open the AMD NPU accel device on Ryzen AI systems can create IOVA-mapped BOs and race teardown, without init-namespace root, once force_iova mode is active.
- UI:NUser interaction, none
- Exploitation requires only the attacker opening the accel device, allocating buffer objects, and closing/releasing them (or duping fds) during driver removal; no separate victim mount, click, or other user interaction is needed.
- S:CScope, changed
- The use-after-free dereferences a freed struct iommu_domain during iommu_unmap()/IOVA teardown; corrupting IOMMU mapping state can break DMA isolation between the NPU and host physical memory, crossing the IOMMU security boundary.
- C:HConfidentiality impact, high
- Use-after-free of the IOMMU domain object and associated iovad metadata via amdxdna_dma_unmap_bo() enables attacker-influenced slab reuse; subsequent iommu_unmap and IOVA allocator dereferences provide arbitrary kernel memory disclosure primitives.
- I:HIntegrity impact, high
- UAF on the IOMMU domain during unmap enables heap grooming to corrupt IOMMU page-table management structures and kernel objects, supporting arbitrary kernel writes, control-flow hijack, and potential redirection of NPU DMA to attacker-chosen pages.
- A:HAvailability impact, high
- Dereferencing and operating on a freed iommu_domain in amdxdna_dma_unmap_bo() causes kernel oops/panic; the race is repeatable whenever GEM objects outlive amdxdna_iommu_fini() during device removal, sustaining denial of service.