Loading vulnerability…
CVE-2024-42096 affects the x86 implementation of the Linux kernel timer-profiling function profile_pc(). The function attempted to attribute time spent in spinlock code to the lock's caller by directly reading words from the current stack and heuristically interpreting them as EFLAGS or a return program counter. This logic relied on a simplified lock-function stack layout that is invalid when lock debugging or other instrumentation introduces stack frames. The resulting invalid stack accesses produced KASAN reports. The fix removes the obsolete stack-layout-dependent inspection logic.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel x86 vulnerability involving profile_pc() stack handling.
A Linux kernel x86 flaw in timer-based profiling's profile_pc() routine. The routine made unsafe assumptions about spinlock-related stack layout and read words directly from the stack, producing KASAN warnings when debugging or other stack frames invalidated those assumptions. The vulnerable logic was removed.
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.