CVE-2024-26939 is a use-after-free race in the Linux kernel Intel DRM/i915 driver VMA lifecycle. A VMA can be destroyed concurrently with asynchronous retirement: after the VMA active counter reaches zero, __active_retire() can continue to deactivate and retire the VMA while i915_vma_destroy() frees it through the parked-GT path. The upstream correction retains an untracked GT wakeref when activating an applicable VMA and releases it asynchronously only after VMA deactivation, preventing GT parking and VMA finalization until retirement completes. Global GTT VMAs are excluded to prevent permanently preventing GPU idle.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Intel i915 VMA use-after-free race flaw.
Use-after-free vulnerability in the Linux kernel Intel i915 VMA implementation during a destroy-versus-retire race.
Linux kernel DRM i915 virtual-memory-area use-after-free condition during a destroy-versus-retire race.
Unknown
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.