Look up another CVE · open CVE-2026-97429 in the interactive tracker
CVE-2026-97429
drm/amdkfd: fix UAF race in destroy_queue_cpsch
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-97429 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 | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
wait_on_destroy_queue() drops locks to wait for queue resume, allowing a concurrent destroy to free the queue. Use is_being_destroyed flag to serialize destruction.
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/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
- What this is
- AMD KFDMAINTAINERS section matched on drivers/gpu/drm/amd/amdkfd/ · amd-gfx@lists.freedesktop.org · Supported
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid, bookworm · linux-6.12?
- ?
- not established - no Makefile entry for the affected file
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.
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
Signals
- Published
- 2026-09-24 (24 days 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.13%, higher than 2.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.5 | 6.6.158 | 090b51e2dabf |
| 6.5 | 6.12.111 | 41144829f464 |
| 6.5 | 6.18.53 | d98c8032c299 |
| 6.5 | 7.2 | ac081deaf16a |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
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 from kfd_ioctl_destroy_queue() via AMDKFD_IOC_DESTROY_QUEUE on /dev/kfd, which calls pqm_destroy_queue() then destroy_queue_cpsch() and wait_on_destroy_queue(); the trigger is that local ioctl, not a remote protocol message.
- AC:LAttack complexity, low
- After kfd_ioctl_runtime_enable() and kfd_ioctl_set_debug_trap() (KFD_IOC_DBG_TRAP_ENABLE then KFD_IOC_DBG_TRAP_SUSPEND_QUEUES) set debug_trap_enabled and is_suspended, wait_on_destroy_queue() drops p->mutex; a sibling thread then issues a second AMDKFD_IOC_DESTROY_QUEUE (or KFD_IOC_DBG_TRAP_DISABLE then destroy) and frees the same struct queue while the first sleeps.
- PR:LPrivileges required, low
- kfd_open() has no capable() check, and AMDKFD_IOC_CREATE_QUEUE, AMDKFD_IOC_DESTROY_QUEUE, AMDKFD_IOC_RUNTIME_ENABLE and AMDKFD_IOC_DBG_TRAP are registered with flags 0; kfd_ioctl_set_debug_trap() skips the ptrace check when target==p, so an unprivileged /dev/kfd (render-group) user can trap, suspend and destroy their own queues.
- UI:NUser interaction, none
- The attacker opens their own /dev/kfd fd, enables debug trap on their own pid via kfd_ioctl_set_debug_trap(), suspends the queue with KFD_IOC_DBG_TRAP_SUSPEND_QUEUES, and issues the concurrent AMDKFD_IOC_DESTROY_QUEUE ioctls; no other user must mount, open, or interact.
- S:UScope, unchanged
- The use-after-free of struct queue in wait_on_destroy_queue()/destroy_queue_cpsch() and the later uninit_queue() in pqm_destroy_queue() stays in the host kernel that runs amdkfd; it is not a KVM/Xen guest-to-host escape or an IOMMU/DMA isolation bypass.
- C:HConfidentiality impact, high
- While wait_on_destroy_queue() still evaluates q->properties.is_suspended, the racing pqm_destroy_queue() path kfree()s the same struct queue via uninit_queue() and its MQD via mqd_mgr->free_mqd(); that slab UAF of kernel queue/MQD objects is an arbitrary-read primitive.
- I:HIntegrity impact, high
- The overlapping destroy_queue_cpsch() then pqm_destroy_queue() path list_del()s q->list and kfree()s both the queue and process_queue_node while the waiter still holds those pointers, so the slab can be sprayed into an arbitrary kernel write or control-flow hijack.
- A:HAvailability impact, high
- Using the freed struct queue in wait_on_destroy_queue() or the rest of destroy_queue_cpsch() (list_del(&q->list), free_mqd, uninit_queue) oopses the kernel; a use-after-free is scored High for availability even when not fully exploited.