CVE-2024-26894 is a missing-release-of-memory flaw in the Linux kernel ACPI processor idle subsystem. In acpi_processor_power_exit(), the CPU idle device is unregistered but its associated allocation is not freed. Repeated execution of the affected CPU idle-device cleanup path can retain allocated kernel memory after the object’s effective lifetime.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ACPI processor-idle memory-leak flaw.
A memory leak in the Linux kernel ACPI processor idle power-exit path.
A low-severity Linux kernel memory leak in the ACPI processor_idle component, specifically in acpi_processor_power_exit().
A Linux kernel ACPI processor_idle memory-leak vulnerability in acpi_processor_power_exit(), caused by failing to free a CPU idle device after it is unregistered. It may cause resource exhaustion, instability, or denial of service. Red Hat rates it Low severity with CVSS 6.0; exploitation requires local access and high privileges.
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.