CVE-2025-38703 Details
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 use-after-free vulnerability has been identified in the Linux kernel's DRM/xe component, specifically related to DMA-fences. When userspace closes a submit queue, the associated timeline name can be freed. If the fence was previously exported to a third party, such as through a sync_fence file descriptor, this can lead to a use-after-free condition when the fence is accessed again. The vulnerability arises because the driver did not comply with the newly established DMA-fence safe access rules, which require a Read-Copy-Update (RCU) grace period between signaling a fence and freeing any data it points to.
The vulnerability has been addressed by making the DRM/xe driver compliant with the DMA-fence safe access rules. Users should update to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde | kernel.org | Patch |
| https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.8, < 6.12.43 >= 6.13, < 6.15.11 >= 6.16, < 6.16.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 24, 2025 | Initial Analysis | [email protected] |
| Sep 4, 2025 | New CVE Received | kernel.org |