CVE-2024-41092 is a potential use-after-free vulnerability in the Linux kernel Intel i915 DRM driver's GGTT fence-register revocation path. In i915_vma_revoke_fence(), fence-register revocation could proceed while completion-request signal callbacks associated with a request using the fence were still executing. The function asserted that the fence activity was idle without first waiting for it, creating a race during VMA eviction, unbinding, destruction, and GEM object cleanup. The fix waits for vma->fence->active to become idle before revoking the fence register.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Potential use-after-free in the Linux kernel Intel i915 graphics driver during fence-register revocation.
Linux kernel Intel i915 potential use-after-free involving fence-register revocation.
Linux kernel Intel i915 potential use-after-free involving fence-register revocation.
Linux kernel Intel i915 potential use-after-free involving fence-register revocation.
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.