CVE-2025-38703

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.

Predictions

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

References

• https://access.redhat.com/errata/RHSA-2026:0793
• https://www.suse.com/security/cve/CVE-2025-38703.html
• https://errata.rockylinux.org/RLSA-2026:0793
• https://security-tracker.debian.org/tracker/CVE-2025-38703
• https://bugzilla.redhat.com/2393157
• https://bugzilla.redhat.com/2401432
• https://bugzilla.redhat.com/2419954
• https://bugzilla.redhat.com/2422788
• https://bugzilla.redhat.com/2422801
• https://errata.almalinux.org/9/ALSA-2026-0793.html