CVE-2026-99312: KVM Flaw Exposes Host Memory on AMD

Security researchers have shown that a guest virtual machine can read around 127 gigabytes of its host server's memory on cloud systems running Linux KVM on AMD processors, in a flaw tracked as CVE-2026-99312. The bug affects only AMD hosts with nested virtualization switched on, and fixed kernels are already available.
The flaw was found by Oren Yomtov, a researcher at security firm Terra Security, who reported it through DigitalOcean's bug bounty programme after demonstrating it on one of the cloud provider's own Droplet virtual machines. DigitalOcean confirmed the exploit worked on its hosts, treated it as critical, and patched its fleet with a live patch, telling customers no action was needed on their part.
How the flaw works
KVM, the hypervisor built into the Linux kernel, keeps each virtual machine isolated with a nested page table that translates the guest's memory addresses into the host's real memory. The processor finds that table through a pointer stored for each virtual CPU.
Some hosts allow a virtual machine to run a virtual machine of its own, a practice known as nested virtualization. When a reset signal called INIT stops the nested machine, KVM failed to restore the outer machine's pointer, leaving it aimed at a page of memory the kernel had already freed. Once the kernel reused that page, the guest could fill it with entries of its own choosing, and the processor followed them as if they were the real table. Because the forged entries could name any physical page on the host, around 127 GB of the server's RAM came within reach of a guest that had never been given it. The first thing the researchers saw coming back from the test Droplet was the host's kernel version banner, followed by the contents of the host's memory, mapped read-only. In a separate test on the researchers' own bare-metal AMD server, with no other customers attached, the guest wrote 32 chosen bytes into a live page of the host kernel's memory.
Both tests needed root access inside a virtual machine controlled by the researchers. An attacker would need the same position, control of a guest on a vulnerable host, rather than just network access to it.
Disclosure timeline
Yomtov reported the flaw to DigitalOcean and the Linux kernel security team in October. The Linux KVM maintainers, told on 21 October, merged a fix on 2 November, and full fixes landed on 17 November. The CVE record appeared on 18 November, and the research went public the following day. Terra Security published a technical analysis and then took it down within hours; The Register understands DigitalOcean asked for the posts to come down because it needed more time to update its Linux systems.
How serious is it?
Severity ratings disagree: the Linux kernel's CVE team scores CVE-2026-99312 at 8.8 out of 10, while Red Hat's preliminary assessment rates it Moderate at 5.6 and The Register puts the CVSSv3 score at 5.5.
The scope is narrow but real. Intel-based KVM hosts are not affected, because the vulnerable code exists only in KVM's support for nested virtualization on AMD. Many cloud providers surveyed by the researchers were not vulnerable because they had not enabled nested virtualization on AMD. There are no reports of the flaw being used outside research, according to VirtFusion, a virtualization platform vendor tracking the issue, and no exploit code has been published.
A flaw born from a fix
The bug was created by a security fix. A 2022 patch for a different nested-virtualization flaw, CVE-2022-3344, switched a reset path back to the outer virtual machine's control block but missed the page-table pointer, and the error then sat in the kernel for just under four years.
What operators should do
The fix lives in the host kernel: it shipped in stable kernel 7.3.5 and long-term kernels 6.18.64 and 6.12.118. Patching the guest operating systems changes nothing, and a host keeps running its old kernel until it is rebooted.
Distribution kernels mostly do not have the fix yet. Debian's security tracker lists the kernels in all of its releases as vulnerable, with a fix only in unstable, and Ubuntu's CVE tracker rates the flaw High with no fixed package released.
Until a fixed host kernel is installed and the host rebooted, the only available protection is to turn nested virtualization off. Nested virtualization is on by default in the kernel's kvm_amd module, so an unpatched host is exposed unless the setting was deliberately changed. Operators can check with cat /sys/module/kvm_amd/parameters/nested, where a value of 1 or Y means it is on, and disable it with options kvm_amd nested=0 in the host's module configuration, followed by a reboot. The trade-off is that guests can then no longer run virtual machines of their own.
Sources: The Hacker News and The Register.