If you run your own KVM hosts on AMD hardware, a guest VM on your servers may be able to read memory it was never given, and the distribution kernels most teams depend on mostly lack the fix. Until you install a patched host kernel and reboot, the only protection is switching off nested virtualization. Customers of managed clouds are in a better position: DigitalOcean says it has already patched its own fleet.

What happened

According to The Hacker News, researcher Oren Yomtov of Terra Security found a flaw in KVM, the hypervisor built into Linux, tracked as CVE-2026-99312. From inside a VM they controlled on DigitalOcean, the researchers read about 127 GB of the host’s memory. On a shared server, that memory can include other customers’ VMs. The flaw affects only AMD hosts with nested virtualization enabled.

The bug is a dangling pointer. When a nested VM is stopped by an INIT reset, KVM fails to restore a pointer to the outer VM’s page table, which maps guest memory to real host memory. Once the kernel reuses the freed page, a guest can fill it with forged entries that point anywhere on the host. A separate write test on the researchers’ own bare-metal server let a guest place 32 chosen bytes into live host kernel memory.

Maintainers were told on October 21 and merged a fix on November 2. Fixed upstream kernels shipped on Tuesday: 7.3.5, 6.18.64 and 6.12.118. Both tests required root inside a guest. VirtFusion reports no use outside research, and no exploit code is public.

Why it matters

Multi-tenant cloud rests on one promise: a hypervisor keeps customers apart. A guest-to-host memory read breaks that promise at the root, and this is the latest in a run of KVM isolation failures this year, including a 16-year-old shadow memory flaw and the PwnEscape networking bug that exposed host memory in Vercel’s sandboxes, as The Hacker News notes.

The origin is also instructive. The researchers say a 2022 fix for another nested-virtualization bug, CVE-2022-3344, missed one pointer and created this flaw, which sat in the kernel for almost four years. Security patches are code too, and this suggests that reviewing fixes deserves the same scrutiny as new features.

Severity scoring is split. The Linux kernel CVE team gives 8.8 out of 10, while Red Hat’s preliminary view is Moderate at 5.6 and treats the impact as denial of service only. The provider treated it as critical for shared cloud. The likely lesson is that severity depends on your threat model: a host running only your own trusted workloads faces less risk than one renting VMs to strangers.

What it means for you

Find your exposure. List every KVM host on AMD processors and check whether nested virtualization is on. VirtFusion’s operator guide says it is on by default in the kvm_amd module, so assume exposure unless someone changed it. Intel hosts are not affected.

Choose a mitigation. Install a fixed host kernel and reboot, because a host keeps running its old kernel until restarted. Patching the guest operating systems does nothing. Where no fixed package exists, turn nested virtualization off. That closes the path completely, but tenants can no longer run VMs inside VMs, so tell anyone who depends on it first.

Check your distribution. Per The Hacker News, Debian lists all its releases as vulnerable with a fix only in unstable, Ubuntu rates the flaw High with no fixed package, and Red Hat lists Enterprise Linux 9 and 10 as affected with the fix deferred. Enterprise Linux 8 is not affected. Plan reboot windows now, since vendor packages may arrive on short notice.

Ask your cloud vendor. If you buy VMs, ask whether the provider runs AMD hosts with nested virtualization and how it patches hosts, including live patching. Also note that no guidance exists for detecting a past attempt, so you cannot confirm a clean history. For wider reading, see our cybersecurity coverage.

What to watch

  • Fixed kernel packages from Debian, Ubuntu and Red Hat, and whether Red Hat reverses its deferral for Enterprise Linux 9 and 10.
  • Publication of exploit code, which would raise the urgency for unpatched hosts.
  • Whether the severity gap between the kernel team’s 8.8 and Red Hat’s 5.6 narrows.
  • Further disclosures of KVM isolation flaws, given the pace this year.

Sources