November 20, 2026 / news

KVM Guest-to-Host Memory Exposure on AMD Hosts (CVE-2026-99312) Fixed in Kernel 7.3.5, 6.18.64 and 6.12.118

CVE-2026-99312: a stale nested page-table pointer in Linux KVM let a guest with root read ~127 GB of AMD host memory on DigitalOcean. Fixed in 7.3.5, 6.18.64 and 6.12.118; unpatched hosts should disable nested virtualization.

Title: Linux KVM Flaw Lets a Guest Read the Host’s Memory on AMD Servers Running Nested Virtualization

Summary: A researcher at Terra Security, Oren Yomtov, showed from root inside a guest VM of his own on a DigitalOcean Droplet that roughly 127 GB of the AMD host’s RAM could be mapped read-only from the guest — with the host’s kernel banner surfacing early in the output — on a machine where nested virtualization was enabled. The bug, filed as CVE-2026-99312, sits in KVM’s nested SVM path: an INIT reset that halts a nested guest leaves the outer vCPU holding a nested page-table pointer that refers to a page the kernel has released, and if that page later gets handed out as a last-level page table, the guest can repopulate it with forged entries naming whatever host physical pages it likes. Terra pins the regression on 2022’s CVE-2022-3344 fix — it put the vCPU back on the outer control block during INIT but overlooked the page-table pointer — so the defect has been present for nearly four years; the vulnerable code arrived with the 6.1 series and was backported to 5.15.81 and 6.0.11. Pulling it off means holding root inside a guest VM, so purely remote attackers are out of scope, and VMX escapes the issue because INIT is intercepted unconditionally there — only AMD nested SVM is exposed. Terra alerted the KVM maintainers on October 21, 2026; the patch reached mainline on November 2, was tagged in v7.4-rc2 on November 9, and landed in stable 7.3.5 plus the long-term 6.18.64 and 6.12.118 on November 17, with the CVE record published November 18. DigitalOcean confirmed the exploit against its own infrastructure, graded the issue critical, live-patched the fleet and told Droplet customers “no action needed on your part”; Terra’s survey of other cloud providers found many were not vulnerable because they had not enabled nested virtualization on AMD. The severity picture is contested: the kernel CVE team assigns 8.8, while Red Hat’s provisional score is 5.6 (Moderate), counting only denial-of-service impact. Most distribution kernels have yet to pick the fix up — Debian shows it only in unstable, Ubuntu’s kernels remain flagged vulnerable with no patched package, and Red Hat has deferred the fix for Enterprise Linux 9 and 10. Until the host runs a patched kernel (which takes effect only after a reboot), disabling nested virtualization is the only complete stopgap: read cat /sys/module/kvm_amd/parameters/nested, add options kvm_amd nested=0 to the module configuration where updating is not yet possible, and reboot — the option applies only at boot and cannot be flipped while guests are running. VirtFusion, which is tracking the issue for its operators, reports no exploitation beyond the research and no public exploit code.

References:

← All news