CVE-2024-40988 is an improper bounds-validation issue in the Linux kernel Radeon DRM driver’s kv_dpm.c code. The code handling sumo_vid_mapping_entry lacked a bounds check, resulting in a UBSAN warning condition. The upstream fix adds bounds validation for this entry.
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.
Linux kernel vulnerability referenced by the advisory.
Linux kernel Radeon DRM issue in kv_dpm.c identified through a UBSAN warning.
Linux kernel Radeon DRM issue in kv_dpm.c that generated a UBSAN warning.
Linux kernel Radeon DRM driver issue in kv_dpm.c identified through UBSAN.
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.