Look up another CVE · open CVE-2026-63840 in the interactive tracker
CVE-2026-63840
drm/amdgpu/jpeg: set no_user_fence for JPEG v5.3.0 ring
Published 2026-07-19 (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-63840 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.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 86ac011ae234c03fb872f4945913391ea1d8862e)
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/jpeg_v5_3_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. 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 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-07-19 (3 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.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 |
|---|---|---|
| 7.0 | 7.0.10 | 46ad73aec27d |
| 7.0 | 7.1 | 3b0ea2021351 |
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 submitting DRM_IOCTL_AMDGPU_CS on a local /dev/dri/renderD* device node; the vulnerable JPEG v5.3.0 ring path is only reachable through this local ioctl interface, not over the network.
- AC:LAttack complexity, low
- An attacker with render-node access can reliably craft an AMDGPU_CS submission with a FENCE chunk targeting the JPEG ring (ip_type=AMDGPU_HW_IP_VCN_JPEG) on VCN/JPEG 5.3.0 hardware without races or conditions outside their control.
- PR:LPrivileges required, low
- DRM_IOCTL_AMDGPU_CS is gated by DRM_AUTH|DRM_RENDER_ALLOW, requiring only unprivileged local access to a render node (typical for users in the render/video group, browser GPU processes, or cloud GPU tenants), not root in the init namespace.
- UI:NUser interaction, none
- No victim interaction is required once the attacker has render-node access; exploitation is achieved entirely through crafted ioctl submissions.
- S:UScope, unchanged
- Impact is confined to the kernel/GPU driver security domain of the compromised context; this is a standard local GPU driver memory-corruption issue, not a VM escape or cross-security-authority boundary bypass.
- C:HConfidentiality impact, high
- The unsupported 64-bit user fence path causes the JPEG engine to perform a GPU-initiated memory write to attacker-chosen GPU virtual addresses, providing a memory-corruption primitive that can be leveraged for arbitrary kernel memory disclosure in exploit chains.
- I:HIntegrity impact, high
- The malformed fence write is a GPU-driven arbitrary memory write to attacker-controlled GPU VA mappings (including GTT-backed system memory), constituting a memory corruption primitive exploitable for code execution or privilege escalation.
- A:HAvailability impact, high
- Triggering unsupported fence operations on the JPEG engine can cause GPU hangs, engine resets, or kernel warnings/oops, resulting in denial of service affecting system availability.