Loading vulnerability…
CVE-2025-38703 is a use-after-free vulnerability in the Linux kernel DRM/Xe graphics driver. Xe can free data referenced by an exported DMA fence, including the timeline name associated with a submit queue, after userspace closes that queue. A separate holder of the exported fence can subsequently access the fence after its referenced data has been freed. The flaw results from Xe not meeting DMA-fence safe-access lifetime requirements. The fix defers queue release using RCU and adds an RCU grace period before freeing the per-GT structure containing a shared lock, ensuring referenced data is not freed until safe after fence signaling.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel drm/xe vulnerability addressed by making dma-fences compliant with safe access rules.
A Linux kernel DRM/Xe issue involving DMA-fence safe-access-rule compliance.
Linux kernel DRM/Xe vulnerability addressed by making DMA fences compliant with safe-access rules.
A use-after-free vulnerability in the Linux kernel's DRM Xe driver caused by freeing data referenced by exported DMA fences without first ensuring an RCU grace period. The fix defers freeing queue and per-GT shared-lock structures to comply with DMA-fENCE safe-access rules.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.