CVE-2026-52951 is a race-condition-driven memory-safety flaw in the Linux kernel drm/xe dma-buf import path. The issue arises because a buffer object can be attached to the dma-buf attachment list before the xe driver has completed full buffer-object initialization. Once attached, the exporter can invoke the invalidate_mappings callback while the associated xe buffer object is still empty, partially initialized, or already freed due to an initialization failure path. This creates two hazardous states: access to an invalid or uninitialized buffer object, and a use-after-free condition if initialization fails after attachment but before the object is safely established. Reported manifestations include NULL pointer dereference during eviction-related handling when importing from another GPU driver such as amdgpu and then triggering eviction flow. The upstream fix defers the attach operation until after the buffer object is fully set up, preventing publication of invalid internal state to dma-buf callback paths.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.