CVE-2025-40134 is a race-condition flaw in the Linux kernel device mapper subsystem. The vulnerability arises in the suspend path, specifically in __dm_suspend(), when a dm device suspend operation races with table loading. If suspend is invoked before table load completes, queue initialization may be only partially finished: queue operations may already be assigned while the associated tag set remains uninitialized. In that state, request-based suspend logic can proceed into queue quiescing and target I/O wait paths and dereference a NULL pointer, leading to a kernel crash. The fix adds validation that a valid device-mapper table is present before performing table-dependent request-based suspend operations and skips those steps when no table has been loaded.
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.
7 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.