Look up another CVE · open CVE-2026-97497 in the interactive tracker
CVE-2026-97497
drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-97497 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 | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| 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
allocate_sdma_queue has an option where the sdma queue id can be specified (used by CRIU). We weren't bounds-checking that value. Confirm it's less than the maximum number of queues.
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
- not yet assignedsource
- 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 |
|---|---|---|
| 5.18 | 6.1.189 | 41460d2dd024 |
| 5.18 | 6.6.158 | 25e1b29ecc8d |
| 5.18 | 6.12.111 | 42f2bd50236b |
| 5.18 | 6.18.53 | dd2870ca036e |
| 5.18 | 7.2 | bfe9a7545b2a |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| 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 unbounded index is kfd_criu_queue_priv_data.sdma_id, copy_from_user'd in kfd_criu_restore_queue() from AMDKFD_IOC_CRIU_OP KFD_CRIU_OP_RESTORE on /dev/kfd, then passed as restore_sdma_id into allocate_sdma_queue() by create_queue_cpsch()/create_queue_nocpsch(); no network protocol carries that field.
- AC:LAttack complexity, low
- A single crafted KFD_CRIU_OP_RESTORE QUEUE object with type KFD_QUEUE_TYPE_SDMA or KFD_QUEUE_TYPE_SDMA_XGMI and an oversized sdma_id makes allocate_sdma_queue() run test_bit()/clear_bit() on that index; the attacker supplies the whole criu_restore() blob, so no race or victim-owned GPU state is required.
- PR:LPrivileges required, low
- kfd_ioctl() admits AMDKFD_IOC_CRIU_OP only when capable(CAP_CHECKPOINT_RESTORE) or capable(CAP_SYS_ADMIN). CAP_CHECKPOINT_RESTORE is the delegated non-root capability already held by CRIU tooling and container checkpoint services, matching limited local privilege rather than init-namespace root.
- UI:NUser interaction, none
- The attacker opens their own /dev/kfd (kfd_open -> kfd_init_apertures creates PDDs) and issues KFD_CRIU_OP_RESTORE against that process; no other user must mount media, open a file, or interact.
- S:UScope, unchanged
- allocate_sdma_queue()'s OOB test_bit()/clear_bit() on the kzalloc'd device_queue_manager sdma_bitmap corrupts host kernel slab inside amdkfd. That stays in the same kernel authority; it is not a KVM/Xen guest-to-host escape or an IOMMU/DMA bypass.
- C:HConfidentiality impact, high
- restore_sdma_id is a user uint32_t used as the bit index into a KFD_MAX_SDMA_QUEUES (128-bit) dqm->sdma_bitmap. test_bit() of an out-of-range index is an unbounded kernel-bit read (the ioctl returns -EBUSY iff the bit is clear), which is not a few-byte leak.
- I:HIntegrity impact, high
- When that out-of-range bit is set, allocate_sdma_queue() does clear_bit(*restore_sdma_id, dqm->sdma_bitmap), a one-bit write at an attacker-chosen offset past the 128-bit map into later dqm fields (fence_addr, hung_db_array) or adjacent kmalloc objects, an OOB write.
- A:HAvailability impact, high
- test_bit()/clear_bit() of a restore_sdma_id whose bitmap word is unmapped oopses inside allocate_sdma_queue(); the same OOB clear can smash dqm pointers and flags and panic the host.