Use-after-free in Linux kernel KVM arm64 nested_mmus reallocation
CVE-2026-46317 is a Linux kernel KVM/arm64 vulnerability in the handling of kvm->arch.nested_mmus[]. The array is walked while holding kvm->mmu_lock, including from the MMU notifier path via kvm_unmap_gfn_range() -> kvm_nested_s2_unmap(), which may execute asynchronously. However, kvm_vcpu_init_nested() could reallocate the nested_mmus array and free the old buffer while holding only kvm->arch.config_lock. This creates a race where concurrent walkers can dereference the freed array, resulting in a use-after-free. The fix allocates a replacement array outside mmu_lock, then under mmu_lock copies existing entries, repairs back pointers, and atomically reassigns the array, with the old buffer freed only after dropping the lock.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.