CVE-2025-37849 is an error-path cleanup flaw in the Linux kernel KVM arm64 implementation. If kvm_arch_vcpu_create() fails while sharing a vCPU page with the hypervisor, KVM returns the error to the vCPU-creation ioctl caller but leaves the associated virtual Generic Interrupt Controller (vGIC) vCPU structures initialized. Subsequent vCPU destruction leaks the associated memory, and redistributor-device handling can dereference the stale vCPU state, producing a use-after-free. The fix destroys the vGIC vCPU structures on the failed vCPU-creation path.
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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Listed as one of 573 vulnerabilities addressed by SUSE-SU-2026:20560-1 for kernel packages in SUSE Linux Micro Extras 6.2.
A Linux kernel KVM arm64 vulnerability involving teardown of vGIC on failed vCPU creation.
A Linux kernel KVM arm64 vulnerability involving failure to tear down the virtual GIC after unsuccessful virtual CPU creation.
A Linux kernel KVM arm64 flaw involving failure to tear down the virtual GIC after failed virtual CPU creation.
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.