Look up another CVE · open CVE-2026-53201 in the interactive tracker
CVE-2026-53201
Revert "drm/xe: Skip exec queue schedule toggle if queue is idle during suspend"
Published 2026-06-25 (4 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-53201 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.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
This reverts commit 8533051ce92015e9cc6f75e0d52119b9d91610b6. The idle-skip optimization bypasses GuC suspend, so the GPU may not perform the context switch that flushes TLB entries for invalidated userptr VMAs. In LR/preempt-fence VM mode, this can lead to missed TLB invalidation and page faults during userptr invalidation tests. Restore unconditional schedule toggling on suspend so the context-switch TLB flush is always performed. This optimization will be reintroduced with a fix that does not skip suspend in LR/preempt-fence VM mode. (cherry picked from commit 6a1e7934d9a6cf46aecae00a99c2603d1295e170)
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/xe/xe_exec_queue.h
drivers/gpu/drm/xe/xe_guc_submit.c
drivers/gpu/drm/xe/xe_hw_engine_group.c
- What this is
- INTEL DRM XE DRIVER (Lunar Lake and newer)MAINTAINERS section matched on drivers/gpu/drm/xe/ · intel-xe@lists.freedesktop.org · Supported
- Kernel module
- xe
Check it on the machine
grep -w CONFIG_DRM_XE /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 xePrints 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 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/cloud-amd64, arm64/arm64-16k, arm64/cloud-arm64, armel/rpi, ppc64el/powerpc64le-64k, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64-16k, arm64/cloud-arm64, loong64/loong64, ppc64el/powerpc64le-64k, 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_XE
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-06-25 (4 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.13%, higher than 2.2% 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.13 | b69b715f48ac |
| 7.0 | 7.1 | fa7c84726dc2 |
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
- Reachability is through local DRM Xe render-node IOCTLs such as VM creation, userptr VM_BIND, exec-queue creation, and EXEC submission. The affected path is not exposed over the network or an adjacent/physical protocol.
- AC:LAttack complexity, low
- The attacker can create the required LR/preempt-fence fault-mode VM, non-parallel idle exec queue, userptr mapping, and invalidation sequence themselves. The idle/suspend condition is attacker-controllable and does not require winning an external race.
- PR:LPrivileges required, low
- The IOCTLs are DRM_RENDER_ALLOW and do not require CAP_SYS_ADMIN or another real root capability. Exploitation requires only a local user able to open the Xe DRM render device.
- UI:NUser interaction, none
- No victim action is required after the attacker has local access to the render node. The attacker can drive queue creation, submission, and userptr invalidation directly.
- S:UScope, unchanged
- The vulnerability affects the same host kernel/GPU memory-management security authority. There is no demonstrated VM escape, IOMMU bypass across guests, or separate security authority transition.
- C:HConfidentiality impact, high
- Missed TLB invalidation can leave stale GPU translations to invalidated userptr pages, allowing GPU commands to read physical pages after they are reused. In the highest reasonable scenario this can disclose arbitrary sensitive memory.
- I:HIntegrity impact, high
- GPU writes through stale translations can corrupt pages after reuse by another process or the kernel. This is a stale DMA-style memory corruption primitive with high integrity impact.
- A:HAvailability impact, high
- The stale translations can trigger GPU page faults, hangs, resets, or broader memory corruption. Repeated triggering can cause high availability impact to the GPU subsystem and potentially the kernel.