CVE-2025-38345 is a memory-leak vulnerability in the Linux kernel ACPICA implementation's ACPI operand-stack cleanup. When ACPI processing terminates early because of a malformed or malicious ACPI table, acpi_ds_obj_stack_pop_and_delete() calculates the operand-stack top inconsistently with acpi_ds_obj_stack_push(). The resulting indexing mismatch can leave ACPI operand objects allocated in the Acpi-Operand slab cache while the system continues booting.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ACPICA flaw in ACPI operand-stack cleanup that causes an operand-cache memory leak when ACPI initialization terminates early, such as after processing a malicious ACPI table. On older kernels (<= 4.9), resulting stack dumps may disclose kernel function addresses that could help defeat kernel ASLR. The referenced Google COS packages are fixed in version 18244.448.6 or later.
Linux kernel ACPICA vulnerability involving an ACPI operand cache leak in dswstate.c.
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.