Look up another CVE · open CVE-2026-63847 in the interactive tracker
CVE-2026-63847
drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring
Published 2026-07-19 (3 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-63847 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.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| 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 3216a7f4e2642bda5fd14f57586e835ae9202587)
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_v2_5.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-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.18%, higher than 6.6% 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.6 | 6.6.141 | 63691e396105 |
| 5.6 | 6.12.91 | 4d96e3cbfc66 |
| 5.6 | 6.18.33 | 3a96fee676fc |
| 5.6 | 7.0.10 | 694fe016969c |
| 5.6 | 7.1 | 79405e774ede |
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 issuing DRM_IOCTL_AMDGPU_CS against /dev/dri/renderD* on a system with an affected AMD Instinct GPU (MI100/MI200); this is a local ioctl path, not reachable over the network.
- AC:LAttack complexity, low
- An attacker with render-node access can deterministically submit a JPEG-ring command buffer (AMDGPU_HW_IP_VCN_JPEG) with an AMDGPU_CHUNK_ID_FENCE chunk; no race or special system state is required beyond the vulnerable hardware being present.
- PR:LPrivileges required, low
- The amdgpu_cs_ioctl entry point requires only DRM render-client access (DRM_AUTH|DRM_RENDER_ALLOW), which is granted to unprivileged local users in the render/video group or cloud GPU tenants with device access—not root or CAP_SYS_ADMIN.
- UI:NUser interaction, none
- Exploitation is fully programmatic via ioctl submission and does not require any action from another user or administrator.
- S:UScope, unchanged
- The corrupting GPU fence write is issued within the attacker's own DRM/GPU context and VM; impact remains within the same security authority and does not constitute a demonstrated VM escape or IOMMU boundary bypass.
- C:HConfidentiality impact, high
- The malformed 64-bit user fence write on unsupported JPEG hardware causes GPU-initiated memory corruption at an attacker-chosen address, which can be leveraged for arbitrary memory disclosure beyond a bounded leak.
- I:HIntegrity impact, high
- The vulnerability gives the attacker a GPU DMA write primitive to user-specified GPU-mapped memory, enabling arbitrary data modification and potential further exploitation such as privilege escalation.
- A:HAvailability impact, high
- Triggering an unsupported 64-bit fence operation on the JPEG engine can cause GPU faults, driver hangs, or kernel oops/panic, impacting system availability.