Look up another CVE · open CVE-2026-46204 in the interactive tracker
CVE-2026-46204
drm/amdgpu/vcn4: Prevent OOB reads when parsing IB
Published 2026-05-28 (5 months 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-46204 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.90-1 | Update the kernel and reboot. Fixed in 6.12.90-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.9-1 | Update the kernel and reboot. Fixed in 7.0.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.9-1 | Update the kernel and reboot. Fixed in 7.0.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Rewrite the IB parsing to use amdgpu_ib_get_value() which handles the bounds checks.
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/vcn_v4_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 -w CONFIG_DRM_AMDGPU /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.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_DRM_AMDGPU
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-05-28 (5 months ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.4% 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 |
|---|---|---|
| 6.0 | 6.6.140 | 1dc005775fb5 |
| 6.0 | 6.12.90 | d0802a8877d7 |
| 6.0 | 6.18.32 | a6d5563ba1f0 |
| 6.0 | 7.0.9 | 5c3e8ebad0c9 |
| 6.0 | 7.1 | 2444eb0ec828 |
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
- Reached only via the local amdgpu command-submission ioctl (DRM_IOCTL_AMDGPU_CS) on a DRM render node; no network or adjacent vector is involved.
- AC:LAttack complexity, low
- The attacker fully controls the IB contents, length_dw, and the backing BO size/layout, so positioning the parser so that idx+6..+8 reads cross the BO's last mapped page is reliably reproducible.
- PR:LPrivileges required, low
- Requires the ability to open the DRM render node and submit command buffers, i.e. an unprivileged local user with GPU/graphics-session access; no elevated capability is needed.
- UI:NUser interaction, none
- The malicious command buffer is submitted directly by the attacker; no action by another user is required.
- S:UScope, unchanged
- Parsing runs on the CPU in kernel context and the OOB access stays within the kernel's own memory; no VM, IOMMU, or sandbox boundary is crossed.
- C:HConfidentiality impact, high
- The unchecked indexing reads kernel memory beyond the IB buffer object (decode_buffer fields and loop words), an out-of-bounds read of kernel memory that is not strictly limited to a couple of bytes.
- I:NIntegrity impact, none
- The flaw is purely an out-of-bounds read; the parser performs no OOB write and the OOB-derived address is re-validated before use, so no kernel data is modifiable.
- A:HAvailability impact, high
- Reading past the BO into an unmapped kernel page faults during command submission, producing a kernel oops/crash that the attacker can trigger on demand.