Look up another CVE · open CVE-2026-52950 in the interactive tracker
CVE-2026-52950
drm/xe/dma-buf: fix UAF with retry loop
Published 2026-06-24 (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-52950 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
Retry doesn't work here, since bo will be freed on error, leading to UAF. However, now that we do the alloc & init before the attach, we can now combine this as one unit and have the init do the alloc for us. This should make the retry safe. Reported by Sashiko. v2: Fix up the error unwind (CI) (cherry picked from commit 479669418253e0f27f8cf5db01a731352ea592e7)
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_dma_buf.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-24 (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.18%, higher than 6.9% 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.18 | 6.18.33 | 39fdac6be02e |
| 6.18 | 7.0.10 | 827062952ed9 |
| 6.18 | 7.1 | 155a372a1cc5 |
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
- Reachable through the local DRM_IOCTL_PRIME_FD_TO_HANDLE ioctl on an Intel Xe DRM device by importing a dma-buf FD into the Xe driver. This is a local syscall/ioctl path, not a network, adjacent, or physical attack surface.
- AC:LAttack complexity, low
- The UAF arises from attacker-triggerable retry/error handling in the dma-buf import path; a local attacker can repeatedly import dma-bufs and create contention/pressure to exercise the retry loop. No condition appears to require an uncontrollable victim action or rare external state.
- PR:LPrivileges required, low
- The ioctl is DRM_RENDER_ALLOW and Xe supports render nodes, with no CAP_SYS_ADMIN, DRM master, or authentication gate in the path. The attacker needs only local access to the DRM render device and a dma-buf FD, so this is low privilege.
- UI:NUser interaction, none
- No victim user action is required once the attacker has local access to the device node. The attacker can invoke the ioctl and drive the relevant dma-buf operations directly.
- S:UScope, unchanged
- The bug corrupts kernel DRM/Xe memory from within the same kernel security authority. It does not inherently cross a VM, IOMMU, or other separate security scope boundary.
- C:HConfidentiality impact, high
- This is a kernel heap use-after-free involving a freed xe_bo/GEM object that can later be reused through cleanup or dma-buf move-notify paths. Such UAF memory corruption is defensibly capable of producing kernel memory disclosure.
- I:HIntegrity impact, high
- The stale xe_bo/GEM pointer can be used after free in object/refcount and move-notify handling, giving a plausible kernel heap corruption primitive. Under the requested scoring rule, this supports arbitrary modification or code execution impact.
- A:HAvailability impact, high
- Even without full exploitation, the UAF can dereference or operate on freed/corrupted kernel objects and crash the kernel. Related Xe dma-buf fixes reported NULL dereferences and crashes in similar paths.