CVE-2026-99312: Linux KVM nested SVM stale MMU context guest-to-host memory access
CVE-2026-99312 is a memory-management vulnerability in Linux KVM's AMD nested virtualization implementation. When KVM emulates INIT while an L2 guest is running with paging disabled (CR0.PG=0), it can return to L1 without resetting the MMU context. Because the MMU page role includes nested guest state, the retained context is no longer valid. A stale nested page-table pointer can reference freed memory; reuse of that memory with attacker-controlled page-table entries can redirect guest translations to host physical memory. This breaks guest-to-host memory isolation and can permit host memory disclosure, corruption, or denial of service. Intel nested VMX is unaffected because INIT is unconditionally intercepted, preventing the affected emulation path while L2 is active.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker with root access inside a guest VM can potentially read or modify host physical memory, compromising host confidentiality, integrity, and availability and potentially exposing other tenants' memory. Research demonstrations read approximately 127 GB of host RAM from a cloud VM and separately modified 32 chosen bytes of live host kernel memory on a researcher-controlled server. Host crashes and denial of service are also possible. Host code execution was not established by the described demonstrations.
Mitigation
If you can’t patch tonight, do this now.
Disable nested virtualization on affected AMD KVM hosts until the fix is active. Configure the kvm_amd module with nested=0 and reboot to apply the configuration. Verify that nested virtualization is disabled. This prevents guest VMs from running nested VMs and blocks the affected exploitation path.
Remediation
Patch, then assume compromise.
Update the virtualization host to a vendor-supported kernel containing the fix that unconditionally resets the KVM MMU context whenever INIT is emulated, including when paging is already disabled. Reboot into the fixed kernel unless an applicable vendor-supported live patch has been deployed and verified. Updating guest operating systems alone does not remediate the host vulnerability. DigitalOcean reported live-patching its fleet and stated that Droplet customers did not need to take action.
Exploits
No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-99312 exploited in the wild?
- As of Nov 22, 2026, Mallory has no reports of CVE-2026-99312 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-99312?
- As of Nov 22, 2026, Mallory has found no public exploit for CVE-2026-99312.
- Is there a patch for CVE-2026-99312?
- Update the virtualization host to a vendor-supported kernel containing the fix that unconditionally resets the KVM MMU context whenever INIT is emulated, including when paging is already disabled. Reboot into the fixed kernel unless an applicable vendor-supported live patch has been deployed and verified.
- How severe is CVE-2026-99312?
- CVE-2026-99312 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.19% (8th percentile) as of Nov 22, 2026.
Recent activity
94 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.