Threat Intelligence

Linux KVM Flaw Let a Guest VM Read 127 GB of Host Memory on AMD Servers

The Hacker News · 20 Nov 2026
Key Takeaway If you run your own KVM hosts on AMD hardware, switch off nested virtualization now unless you need it, and plan a host kernel update and reboot once your distribution releases a fix.

Researchers have shown that a flaw in KVM, the hypervisor built into the Linux kernel, can let a guest virtual machine (VM) reach memory it was never given. Tracked as CVE-2026-99312, it affects only hosts with AMD processors and nested virtualization enabled. On DigitalOcean, the researchers read about 127 GB of a cloud server's memory from a VM of their own. On a shared server, that memory can include other customers' VMs.

Oren Yomtov of Terra Security found the flaw and reported it through the provider's bug bounty program. The provider confirmed the exploit worked and treated it as critical. It patched its own fleet with a live patch and told Droplet customers no action was needed. A separate write test on the researchers' own bare-metal server let a guest write 32 chosen bytes into the host kernel's memory. Both tests began with root access inside a VM, so an attacker would need control of a guest on a vulnerable host.

The cause is a pointer left pointing at freed memory. When a reset signal called INIT stops a nested VM, KVM skips restoring a pointer for the outer VM. Once the kernel reused that memory, the guest could fill it with forged entries that the processor treated as real, which exposed host memory. The bug was introduced by a 2022 fix for a different flaw and sat in the kernel for almost four years.

Fixed kernels shipped upstream in 7.3.5, 6.18.64 and 6.12.118, but distribution kernels mostly lack the fix. Debian and Ubuntu list their kernels as vulnerable, and Red Hat lists Enterprise Linux 9 and 10 as affected with the fix deferred. Updating the systems inside VMs changes nothing, and a host needs a reboot to load a new kernel. Until then, turning nested virtualization off is the only protection. There are no reports of use outside research, no exploit code is public, and there is no guidance for detecting past attempts.

Why it matters

The flaw breaks the assumption that a guest VM, even one with root access, cannot reach the host or its neighbours, which matters most to anyone hosting multiple tenants on self-managed AMD KVM servers. Patching inside the VMs does nothing, and distribution fixes are mostly unavailable, so operators must decide between disabling nested virtualization and leaving hosts exposed. With no detection guidance for past attempts, the risk cannot be ruled out after the fact.

What to do

  • Disable nested virtualization on AMD KVM hosts until a fixed kernel is installed, after warning tenants who rely on it.
  • Update host kernels to 7.3.5, 6.18.64 or 6.12.118 or a distribution build containing the fix, then reboot the host.
  • Check which hosts run AMD processors with the kvm_amd module, where nested virtualization is on by default.
KVM CVE-2026-99312 virtualization AMD cloud security Linux kernel

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.