Skip to main content
Mallory
HighVulnerability

CVE-2026-99312: Linux KVM nested SVM stale MMU context guest-to-host memory access

Published Nov 18, 2026 · Updated today
Trending this week#37of 432,046 vulnerabilities
Mention activity · 30 days94 mentions · peak 37 in a dayToday
CVSS8.8High · v3.1
EPSS0.19%8th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-99312CWE-416

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

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.
Activity feed

Recent activity

94 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tuxcare security updatesNews · Nov 21, 2026CLSA-2026:1795250851A KVM x86 flaw addressed by unconditionally resetting the MMU context during INIT emulation.Read more ↗the hacker newsNews · Nov 20, 2026Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD HostsA stale nested-page-table pointer in Linux KVM's AMD nested-virtualization support lets an attacker with root access inside a guest VM access arbitrary host physical memory. Researchers demonstrated reading approximately 127 GB of a DigitalOcean host's memory and modifying host kernel memory on their own server. An INIT reset leaves a pointer referencing freed memory, allowing guest-controlled page-table entries to bypass VM isolation. Fixed upstream kernels include 7.3.5, 6.18.64, and 6.12.118, but several distribution kernels remained unpatched at publication. Operators should install a fixed host kernel and reboot, or disable nested virtualization.Read more ↗register securityNews · Nov 20, 2026Flaws in VMware and KVM need attention, if you have time while fixing Java, PHP, and everything elseA Linux KVM vulnerability affecting AMD-based systems using nested virtualization. A guest VM can attack its host through denial of service or memory corruption. A researcher reported accessing 127 GB of host RAM from a Digital Ocean Droplet. The reported CVSSv3 score is 5.5. Kernel fixes are available, and disabling nested virtualization mitigates the issue. The article describes researcher testing, not confirmed malicious exploitation in the wild.Read more ↗tenable nessus pluginsNews · Nov 20, 2026Oracle Linux 8 / 9 : Unbreakable Enterprise kernel (ELSA-2026-... | Tenable®A vulnerability covered by the Unbreakable Enterprise Kernel advisory ELSA-2026-500643 for Oracle Linux 8 and 9. The excerpt does not describe the underlying flaw. Patches were published on November 19, 2026, and the plugin states that no known exploits are available.Read more ↗
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity88Community discussion across Reddit, Mastodon, and other social sources.