Loading vulnerability…
CVE-2025-22013 is an arm64 Linux KVM context-management flaw caused by lazy saving of host FPSIMD, SVE, and SME state in hypervisor code. Inconsistent handling of host SVE configuration, including TIF_SVE and CPACR_ELx.ZEN state, can cause host SVE state to be discarded unexpectedly. The lazy-discard path can also discard host SVE state after ptrace modifies it, changing the ptrace ABI, and can leave a stale host FPMR value when a non-protected VM uses FPSIMD or SVE without FPMR being exposed to that VM. The correction eagerly saves and flushes host FPSIMD/SVE/SME state whenever a vCPU is loaded, preventing KVM from later relying on lazy host-state preservation.
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.
1 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.