Linux KVM flaw CVE-2026-99312 lets a guest VM read host memory on AMD hosts with nested virtualisation

· CyberSecurity

TLDR

  • Researchers read about 127 GB of a DigitalOcean host's memory from inside a guest VM on AMD hardware.23
  • Fixes shipped in kernels 7.3.5, 6.18.64 and 6.12.118; switching nested virtualisation off is the stated workaround.234
  • Debian's tracker lists bookworm, trixie and forky kernels as vulnerable; Ubuntu's lists 22.04 LTS and later as vulnerable.67

A flaw in KVM, the hypervisor built into the Linux kernel, let Terra Security researcher Oren Yomtov read about 127 GB of a DigitalOcean host's memory from inside a virtual machine of their own, The Hacker News reports.1 The flaw is tracked as CVE-2026-99312 and affects hosts with AMD processors and nested virtualisation enabled.12 DigitalOcean says a root user inside a Droplet could reach and modify the physical host's memory, which on a shared host includes other tenants' VMs; it showed the read on one of its Droplets and the write on a bare-metal AMD server with no other customers.3 The Linux kernel CVE team published the CVE announcement, titled "KVM: x86: Unconditionally reset MMU context when emulating INIT", on 18 November 2026.4

Terra's write-up, dated 18 November, says that when a reset signal called INIT stops a nested VM, KVM skips the update that points the guest's nested page table pointer back at its live table.2 The guest resumes with a pointer to a page the kernel has since freed, and once KVM reuses that page the guest can fill it with entries of its own choosing.2 Terra says it pointed such a forged table at about 127 GB of DigitalOcean host RAM, mapped read-only, and found the host's kernel version banner.2 The write was shown on Terra's own AMD server, where the guest put chosen bytes into a host kernel page, and DigitalOcean puts the write at 32 bytes.23 The kernel announcement says the bug affects only nested SVM, because INIT is an unconditional intercept on Intel's VMX.4 The Hacker News reports that both tests started with root access inside a VM the researchers controlled.1

Terra and DigitalOcean both say the flaw was opened by the 2022 fix for CVE-2022-3344, which missed the pointer, and that it sat in the kernel for just under four years.23 Terra's timeline gives 21 October as the report to the Linux KVM maintainers, 2 November as the mainline merge, 9 November as the first tag in v7.4-rc2, and 17 November as the release in stable 7.3.5 and the 6.18.64 and 6.12.118 long-term kernels.2 The kernel announcement lists the issue as introduced in 6.1, with 5.15.81 and 6.0.11 also listed.4 DigitalOcean says it validated the exploit on its own hosts, treated it as critical, and rolled out a live patch across its fleet, so Droplet customers need take no action.3 Operators running their own AMD KVM hosts are told to update to a kernel carrying the fix or, if they cannot, set the nested parameter of the kvm_amd module to 0.23 Red Hat's page gives the same mitigation and notes that disabling it requires shutting down all running VMs first; The Hacker News adds that a host keeps running its old kernel until it is rebooted.15 Terra says many cloud providers it surveyed were not vulnerable because they had not enabled nested virtualisation on AMD.2

Debian's security tracker lists the bookworm, trixie and forky kernels as vulnerable and a fix only in sid, at 7.3.5-1.6 Ubuntu rates the flaw High and lists the main kernel package as vulnerable on 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10, and not affected on 20.04 LTS and earlier.7 The Hacker News reports that Red Hat lists the Enterprise Linux 9 and 10 kernels as affected with the fix deferred and the Enterprise Linux 8 kernel as not affected.1 The Hacker News reports that VirtFusion, a virtualisation platform vendor tracking the issue, knows of no use of the flaw outside research, and says no exploit code has been published.1

The Linux kernel CVE team scores the flaw 8.8 out of 10, The Hacker News reports, and Red Hat's page shows 8.8 under cve.org.15 The same page lists Red Hat's own CVSS v3 base score as 7.8, marked preliminary and subject to review.5 The Hacker News instead reports that Red Hat's preliminary assessment rates the flaw Moderate at 5.6 and treats the impact as denial of service only; the two figures conflict, so check Red Hat's page for its current rating.15 Red Hat's statement says exploitation requires nested virtualisation on AMD-based KVM hosts and specific guest execution conditions.5 DigitalOcean treated the flaw as critical for its own shared cloud.3

Why it matters: operators of their own AMD KVM hosts with nested virtualisation enabled are told by Terra and DigitalOcean to update the host kernel or switch the feature off.23

Sources

  1. Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts (The Hacker News)
  2. CVE-2026-99312: KVM Guest-to-Host Escape (Terra Security)
  3. Virtualization, Responsible Disclosure, and CVE-2026-99312 (DigitalOcean)
  4. CVE-2026-99312: KVM: x86: Unconditionally reset MMU context when emulating INIT (linux-cve-announce (Linux kernel CVE team))
  5. CVE-2026-99312 - Red Hat Customer Portal (Red Hat)
  6. CVE-2026-99312 (Debian Security Tracker)
  7. CVE-2026-99312 (Ubuntu)