Look up another CVE · open CVE-2026-64516 in the interactive tracker
CVE-2026-64516
drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets
Published 2026-07-25 (3 months 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-64516 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.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
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/amdgpu/vce_v1_0.c
- What this is
- RADEON and AMDGPU DRM DRIVERSMAINTAINERS section matched on drivers/gpu/drm/amd/ · amd-gfx@lists.freedesktop.org · Supported
- Kernel module
- amdgpu
Check it on the machine
grep -wE 'CONFIG_DRM_AMDGPU|CONFIG_DRM_AMDGPU_SI' /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 amdgpuPrints 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/cloud-arm64, 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_AMDGPU, CONFIG_DRM_AMDGPU_SI
- 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-07-25 (3 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.4% 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.19 | 7.0.11 | ce0de178ef08 |
| 6.19 | 7.1 | 3e5a1d5bb2ff |
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
- An attacker reaches VCE1 through DRM command-submission ioctls on the local render device; there is no network or physical attack path.
- AC:LAttack complexity, low
- An attacker can repeatedly submit VCE jobs and control session allocation and engine power-up without winning an uncontrollable race or relying on an unusual runtime condition.
- PR:LPrivileges required, low
- The AMDGPU_CS ioctl is DRM_RENDER_ALLOW and contains no capability or DRM-master requirement, so ordinary users with render-node access can reach it.
- UI:NUser interaction, none
- Exploitation requires only attacker-controlled ioctl submissions and does not depend on another user opening content or performing an action.
- S:CScope, changed
- The VCE VCPU operates through direct GPU/GART addresses with its VM control disabled, so access beyond the kernel VCPU BO crosses the GPU DMA memory-isolation boundary.
- C:HConfidentiality impact, high
- The oversized and misaligned read/write cache windows can expose adjacent VRAM or GART-backed memory outside the VCPU BO, potentially permitting disclosure of high-value memory.
- I:HIntegrity impact, high
- The VCE data and stack windows are writable, so their out-of-bounds placement can corrupt adjacent GPU or GART-backed allocations and potentially affect execution or protected data.
- A:HAvailability impact, high
- The invalid firmware layout can cause VCE VM faults, firmware failure, or a GPU/card lockup, and an unprivileged attacker can repeatedly reactivate the engine to reproduce the disruption.