CVE-2025-38703

drm/xe: Make dma-fences compliant with the safe access rules

HIGH
7.8
CVSS Score
Published: September 4, 2025 at 03:32 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions6.13 ≤ v < 6.15.116.16 ≤ v < 6.16.26.8 ≤ v < 6.12.436.8dd08ebf6c3525a7ea2186e636df064ea47281987
Vendor states this is fixed in 683b0e397dad9f26a42dcacf6f7f545a77ce6c06 (fixed)
Vendor states this is fixed in 6bd90e700b4285e6a7541e00f969cab0d696adde (fixed)
Vendor states this is fixed in b17fcce70733c211cb5dabf54f4f9491920b1d92 (fixed)
Vendor states this is fixed in ba37807d08bae67de6139346a85650cab5f6145a (fixed)
Vendor states this is fixed in 6.12.43 (unaffected)
Vendor states this is fixed in 6.15.11 (unaffected)
Vendor states this is fixed in 6.16.2 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card