CVE-2025-38703

Source
https://cve.org/CVERecord?id=CVE-2025-38703
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-38703.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-38703
Downstream
Related
Published
2025-09-04T15:32:54.779Z
Modified
2026-03-20T12:42:59.032947Z
Summary
drm/xe: Make dma-fences compliant with the safe access rules
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38703.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
dd08ebf6c3525a7ea2186e636df064ea47281987
Fixed
b17fcce70733c211cb5dabf54f4f9491920b1d92
Fixed
ba37807d08bae67de6139346a85650cab5f6145a
Fixed
683b0e397dad9f26a42dcacf6f7f545a77ce6c06
Fixed
6bd90e700b4285e6a7541e00f969cab0d696adde

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-38703.json"