Protect.Computer
NEWS

Linux KVM Flaw Let a Cloud VM Read 127 GB of Host Memory

· 3 min read · Device safety Network safety
Linux KVM Flaw Let a Cloud VM Read 127 GB of Host Memory

A flaw in KVM, the hypervisor built into the Linux kernel, let researchers read about 127 GB of a cloud server’s memory from inside a virtual machine they controlled on DigitalOcean. The flaw, CVE-2026-99312, affects hosts with AMD processors that have nested virtualization turned on. On a shared host, that memory can belong to other customers’ virtual machines. Oren Yomtov of Terra Security found it and reported it through DigitalOcean’s bug bounty program.

The cause is a stale pointer. When a reset signal called INIT pulls a virtual CPU out of a nested VM, KVM skipped one step and left the outer VM’s page-table pointer aimed at memory the kernel had already freed. Once the kernel reused that page, a guest could fill it with its own entries, and the processor followed them as if they were real. DigitalOcean says the bug sat in the kernel for just under four years: a 2022 fix for CVE-2022-3344 repaired a related problem and missed this pointer. In Terra’s tests, a guest with root access read the host’s kernel version banner and then about 127 GB of host RAM, read-only, on DigitalOcean; on the researchers’ own bare-metal AMD server, with no other customers, it wrote 32 chosen bytes into a live host kernel page.

An attacker needs root inside a guest on a vulnerable host, not just network access. According to The Hacker News, VirtFusion, a virtualization vendor tracking the issue, knows of no use outside research, and no exploit code has been published. Terra’s own write-up does describe the mechanism in detail. Severity ratings differ: The Hacker News says the Linux kernel’s CVE team scores it 8.8, while Red Hat rates it Moderate (5.6 per The Hacker News) and describes the impact as denial of service only. DigitalOcean treated it as critical for its shared cloud.

How to check if you’re affected

Affected products are Linux hosts running KVM on AMD processors with nested virtualization enabled. Red Hat says Intel-based KVM hosts and systems without nested AMD virtualization are not affected, and Terra says many cloud providers it surveyed did not enable nested virtualization on AMD and so were not vulnerable.

If you rent virtual machines, the host kernel is your provider’s job. DigitalOcean says it patched its own fleet with a live patch and told Droplet customers “No action needed on your part.” The sources do not say how other providers are handling it.

If you run your own AMD KVM hosts, DigitalOcean and Terra give two options:

  1. Update the host kernel to one that carries the fix: stable 7.3.5, or the long-term 6.18.64 or 6.12.118 and later.
  2. If you cannot update yet, set the nested parameter of the kvm_amd module to 0, which turns nested virtualization off and closes this path completely.

Neither page gives commands for either step. Our own suggestion, not from the sources: distributions often backport fixes without changing the upstream version number, so check your distribution’s security tracker for CVE-2026-99312 as well as the kernel version, and check the module’s current nested setting before deciding which option applies. The Hacker News notes that no guidance exists for detecting a past attempt.

Terra’s disclosure timeline: reported to the KVM maintainers on October 21, fix merged to mainline on November 2 and tagged in v7.4-rc2 on November 9, released in the stable and long-term kernels on November 17, and CVE-2026-99312 published on November 18. Terra Security sells security products, and DigitalOcean is the provider whose infrastructure was tested.

Sources

Related earlier coverage of a different guest-to-host flaw: PwnEscape: Linux Kernel Flaw Lets VMs Read Host Memory.

Related reading