All reports
Medium

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

Affected versions

Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-38703

Probability of exploitation in the next 30 days: 0.18%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's Intel Xe graphics driver. When an application closes a graphics submission queue, the driver prematurely releases memory tied to exported synchronization objects while other processes are still referencing them. A local user with access to graphics hardware (GPU) could exploit this use-after-free vulnerability to escalate privileges or cause a Denial of Service (DoS) by crashing the system.