Look up another CVE · open CVE-2026-72360 in the interactive tracker
CVE-2026-72360
drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays
Published 2026-08-15 (2 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-72360 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 | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Currently defined VF/PF relay actions use regular REQUEST messages only and the PF shouldn't attempt to handle FAST_REQUEST nor EVENT messages as this would result in breaking the VFPF ABI protocol and also might trigger an assert on the PF side. (cherry picked from commit 1714d360fc5ae2e0886a69e979095d9c7ff3568a)
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_guc_relay.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-08-15 (2 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 6.0% 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 |
|---|---|---|
| 6.11 | 6.12.97 | 499be4b5d642 |
| 6.11 | 6.18.40 | adc7dda728ca |
| 6.11 | 7.1.5 | a4208d8032ab |
| 6.11 | 7.2 | ed8b0d731892 |
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
- A malicious VM guest with an assigned Intel Xe SR-IOV VF reaches the bug by sending crafted GuC relay messages through the local VF-to-PF driver path (guest kernel/driver to host PF via GuC), not over a remote network protocol.
- AC:LAttack complexity, low
- Once assigned an Xe SR-IOV VF, a cloud GPU tenant can reliably inject FAST_REQUEST or EVENT relay messages (e.g., via a modified guest driver) and control both sides of the transaction without uncontrollable timing or memory-layout races.
- PR:LPrivileges required, low
- Exploitation requires tenant-level access to a VM with a passthrough Xe SR-IOV VF (typically root or a custom guest kernel/driver to craft non-REQUEST relay types) but does not require host administrator privileges on the PF.
- UI:NUser interaction, none
- No separate victim action is required; the attacker triggers the flaw directly by sending malformed FAST_REQUEST or EVENT relay messages from their own guest environment.
- S:CScope, changed
- A malicious VF guest causes the host PF kernel driver to mishandle GuC relay messages, crossing the VM/hypervisor security boundary in SR-IOV GPU virtualization (guest-to-host impact on the PF).
- C:NConfidentiality impact, none
- No memory corruption or out-of-band read occurs; VF2PF handshake and runtime-query handlers return the same bounded register data as legitimate REQUEST messages, with no additional confidentiality impact.
- I:HIntegrity impact, high
- FAST_REQUEST and EVENT messages are type-confused with REQUEST and routed to xe_gt_sriov_pf_service_process_request(), causing the PF to emit protocol-invalid responses that corrupt host VF/PF relay and GuC communication state.
- A:HAvailability impact, high
- Violating the VF/PF relay ABI by replying to EVENT/FAST_REQUEST messages can desynchronize host GuC relay handling and trigger PF asserts (drm_WARN on debug builds), risking host GPU driver failure or denial of service affecting all tenants on the device.