Skip to main content
Mallory
Unrated

Use-after-free in Linux kernel KVM arm64 nested_mmus reallocation

IdentifiersCVE-2026-46317CWE-416

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation can trigger a use-after-free in the host kernel's KVM/arm64 subsystem, leading to kernel memory corruption. Depending on allocator state and race reliability, impact may include host kernel crashes or denial of service, and potentially host-kernel privilege escalation or code execution.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or avoiding affected KVM/arm64 nested virtualization functionality where feasible, and limiting untrusted guest workloads on vulnerable arm64 KVM hosts. Because the bug is in host kernel KVM code and involves an internal race with MMU notifier activity, there is no complete mitigation short of applying the kernel fix.

Remediation

Patch, then assume compromise.

Upgrade to a Linux kernel release containing the fix for CVE-2026-46317. The remediation is to perform nested_mmus array reassignment under kvm->mmu_lock, copying existing entries and fixing back pointers before swapping the pointer, and freeing the old allocation only after releasing the lock. Apply the upstream patch referenced for this CVE if running an affected kernel.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.