CVE-2024-42096 is an unsafe stack-reading vulnerability in the Linux kernel's x86 profile_pc() function, used for timer-based profiling. To attribute time spent in spinlocks to their callers, the function reads one or two words directly from the stack pointer and attempts to distinguish EFLAGS values from return program counters. This logic assumes that lock functions have no stack frame or only an EFLAGS copy produced by PUSHF. Lock debugging and other instrumentation can invalidate that assumption, causing invalid stack accesses and Kernel Address Sanitizer (KASAN) warnings. The fix removes the stack-layout-dependent profiling 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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel x86 timer-based profiling flaw in profile_pc() relies on invalid stack-layout assumptions when attributing time spent in spinlocks to their callers. The fix removes the problematic stack-inspection code. The advisory rates the vulnerability Medium, with a CVSS v3 score of 5.5 reflecting local access, low privileges, and high availability impact.
Linux kernel vulnerability covered by the security update.
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.