Look up another CVE · open CVE-2026-72093 in the interactive tracker
CVE-2026-72093
accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap()
Published 2026-08-15 (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-72093 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 vm_insert_pages() fails, the error path calls vma->vm_ops->close(vma) which internally calls drm_gem_vm_close() → drm_gem_object_put(), releasing the GEM object reference acquired at the start of the function. However, the close_vma label then falls through to put_obj, which calls drm_gem_object_put() a second time on the same object. If the first put releases the last reference, the object is freed and the second put accesses freed memory, causing a use-after-free. Fix by returning directly from close_vma instead of falling through to put_obj, since the close handler already performs all necessary cleanup including the object put.
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_gem.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-15 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.8% 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 |
|---|---|---|
| 6.16 | 6.18.40 | 4e370b528962 |
| 6.16 | 7.1.5 | 5da885c39baa |
| 6.16 | 7.2 | 63bbf9ac5dde |
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
- Exploitation requires local DRM ioctls (AMDXDNA_CREATE_BO, PRIME_HANDLE_TO_FD, GEM_CLOSE) and mmap() on the exported dma-buf fd through /dev/accel/accel*; amdxdna_gem_dmabuf_mmap() has no network, adjacent-radio, or physical-bus entry point.
- AC:LAttack complexity, low
- After exporting a BO and closing its GEM handle (leaving only the dma-buf ref), the vm_insert_pages() error path deterministically double-puts the object; the attacker can force insert failure via RLIMIT_AS/cgroup memory pressure without uncontrollable races or victim-specific state.
- PR:LPrivileges required, low
- CREATE_BO and PRIME ioctls are registered without DRM_ROOT_ONLY/AUTH; any unprivileged local user permitted to open the AMD XDNA accel node (typically render/video group on Ryzen AI systems) can create, export, and mmap buffers without real root or init-namespace capabilities.
- UI:NUser interaction, none
- The attacker opens the accel device, creates and exports a buffer, closes the handle, and mmap()s the dma-buf fd in their own process; no separate victim mount, file open, or other user interaction is required.
- S:UScope, unchanged
- The double drm_gem_object_put() use-after-free corrupts kernel slab metadata within the same kernel security authority; it is not a VM escape, hypervisor breakout, or IOMMU DMA-boundary bypass as a direct consequence of this refcount bug.
- C:HConfidentiality impact, high
- UAF on the freed drm_gem_object during the second drm_gem_object_put() lets an attacker reclaim slab objects via heap grooming, enabling arbitrary kernel memory disclosure beyond a bounded metadata leak.
- I:HIntegrity impact, high
- The erroneous second put on a freed GEM object provides slab corruption primitives that can be developed into arbitrary kernel writes and local privilege escalation, not merely limited data modification.
- A:HAvailability impact, high
- The use-after-free in drm_gem_object_put() dereferences freed kmem and can immediately provoke kernel oops/panic; repeated triggering sustains denial of service on the NPU host.