Loading vulnerability…
CVE-2025-54518 is an improper isolation vulnerability affecting shared resources in the CPU operation cache of some AMD Zen 2-based processors. A local, low-privileged attacker may corrupt instructions executed at a higher privilege level, potentially resulting in privilege escalation. The issue is addressed through Linux kernel and Xen security updates for affected platforms.
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.
69 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Xen vulnerability covered by the Debian 12 security update. The advisory collectively describes privilege escalation, information disclosure, or denial of service; this CVE's specific mechanism and impact are not provided.
A privilege-escalation vulnerability affecting Xen environments on AMD Zen 2 processors due to improper CPU-cache isolation.
Linux kernel netfilter nf_tables hook-list handling vulnerability.
A Zen 2 CPU operation-cache isolation flaw that can permit instruction corruption across privilege levels and potential local privilege escalation.
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.