CVE-2024-49570 is a potential use-after-free in the Linux kernel DRM/Xe tracing subsystem. The xe_bo_move trace event deferred dereferencing entries in the xe_mem_type_to_name array until TP_printk formatting time. The deferred dereference could access memory after its lifetime had ended. The fix avoids dereferencing this array during TP_printk processing. Due to related refactoring, applying the correction to kernel versions earlier than 6.10 may require an explicit backport.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Xe DRM tracing use-after-free vulnerability.
Linux kernel DRM/Xe tracing potential use-after-free vulnerability.
A potential use-after-free vulnerability in the Linux kernel's DRM Xe graphics-driver tracing code. The xe_bo_move trace event could dereference the xe_mem_type_to_name[] array during TP_printk processing. The fix avoids that dereference; explicit backporting may be required for kernels older than 6.10.
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.