CVE-2025-38345 is a Linux kernel vulnerability in ACPICA's dswstate.c that causes ACPI operand objects to be leaked during ACPI interpreter early termination. The flaw is triggered when ACPI initialization aborts because of a malformed or malicious ACPI table, but the kernel continues the boot process. The root cause is a stack index mismatch: acpi_ds_obj_stack_push() uses walk_state->operand_index as the top-of-stack position, while acpi_ds_obj_stack_pop_and_delete() incorrectly treats index 0 as the top. This miscalculation prevents proper cleanup of operand objects and leaves entries in the Acpi-Operand slab cache. On affected systems, kernel teardown can report a remaining-object cache leak during ACPI termination.
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.
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.