Look up another CVE · open CVE-2026-63853 in the interactive tracker
CVE-2026-63853
drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc 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-63853 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 | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| 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
VCN encoder and decoder rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit fd852c048b46f9825e904a4f3f4538fe9d8827d9)
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-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 6.3% 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.19 | 6.18.33 | 1286b6872de0 |
| 5.19 | 7.0.10 | 6bdd2ed6458d |
| 5.19 | 7.1 | 51f694221047 |
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 a crafted AMDGPU command stream through DRM_IOCTL_AMDGPU_CS on a local /dev/dri/renderD* device; there is no network, adjacent-radio, or physical-access path to the vulnerable VCN v4.0 unified encoder ring handling.
- AC:LAttack complexity, low
- An attacker with render-node access can deterministically submit a CS containing an AMDGPU_CHUNK_ID_FENCE chunk targeting the VCN encoder ring; no race, special timing, or victim state beyond having a VCN 4.0-capable AMDGPU is required.
- PR:LPrivileges required, low
- The path is reachable by any local user who can open the DRM render node (typically membership in the render/video group on desktops, workstations, and cloud GPU VMs); it does not require real root in the init namespace.
- UI:NUser interaction, none
- Triggering the bug is fully programmatic via ioctl-based CS submission and does not require any victim to open files, mount filesystems, or perform other interactive actions.
- S:UScope, unchanged
- Impact is confined to the AMDGPU/VCN driver and GPU resources of the submitting security context; it does not cross a VM, container, or IOMMU security boundary to affect a different authority.
- C:HConfidentiality impact, high
- Without the no_user_fence guard, amdgpu_ib_commit emits a 64-bit user fence (AMDGPU_FENCE_FLAG_64BIT) on a ring whose emit_fence path only supports 32-bit fence writes, causing the VCN hardware to perform an unvalidated GPU DMA write that can corrupt adjacent GPU-mapped memory and be leveraged for information disclosure.
- I:HIntegrity impact, high
- The same rogue GPU-initiated fence write is a memory-corruption primitive that can modify GPU-accessible buffers (including shared dma-buf mappings) outside the intended 8-byte fence field, enabling integrity violations and potential further exploitation.
- A:HAvailability impact, high
- Malformed fence/trap commands on the VCN unified encoder ring can hang or fault the VCN block and force GPU/driver reset, denying graphics and compute availability to all users of the device on shared workstations and servers.