CVE-2024-31076 is a resource-leak flaw in Linux kernel genirq CPU-hotplug and x86 interrupt-vector handling. Following a deferred interrupt-affinity move, an interrupt vector is allocated on the destination CPU while the previous vector remains pending reclamation on the source CPU. If the source CPU is offlined before the interrupt fires on the destination CPU, the CPU-offline path can skip irq_force_complete_move() because the interrupt is no longer currently affine to the outgoing CPU. Subsequent cleanup on the destination CPU clears move state without reclaiming the prior vector from the vector matrix, leaking the vector.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel x86 interrupt-vector leak during CPU offline operations.
A Linux kernel genirq/CPU-hotplug and x86 vector-management flaw involving vector leakage during CPU offlining.
Linux kernel genirq/cpuhotplug and x86 vector-handling flaw that can leak vectors during CPU offlining.
Linux kernel x86 interrupt-vector resource leak during CPU offline operations.
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.