Linux KVM Flaw CVE-2026-99312 Exposes Host Memory to Guest VMs on AMD Systems

A vulnerability in the Linux Kernel-based Virtual Machine (KVM) hypervisor tracked as CVE-2026-99312 allows attackers with root access inside a guest VM to read and in some cases write to host memory on AMD processors when nested virtualization is enabled. Researchers demonstrated the issue on DigitalOcean infrastructure, successfully dumping approximately 127 GB of host RAM and confirming arbitrary writes into live kernel pages. The root cause traces to a pointer left referencing freed memory after an INIT reset in nested virtualization handling, introduced by an incomplete 2022 fix for CVE-2022-3344. The flaw affects only AMD-based hosts; Intel systems remain unaffected because the vulnerable code path exists solely in KVM's AMD nested virtualization support. Fixed kernels were merged upstream on November 2 and released in stable and long-term branches on November 19, while DigitalOcean applied live patches to its fleet. Severity ratings vary, with the Linux kernel CVE team assigning 8.8 and Red Hat rating it Moderate at 5.6. Operators are advised to update host kernels or disable nested virtualization via the kvm_amd module parameter.

The Hacker NewsTranslated from English

Read at source

A flaw in KVM, the hypervisor built into the Linux kernel, allowed researchers to read about 127 GB of a cloud server's memory from inside a virtual machine on DigitalOcean. On a shared server, that memory can include other customers' virtual machines.

The flaw, tracked as CVE-2026-99312, affects only hosts with AMD processors and nested virtualization enabled. Fixed kernels shipped upstream on Tuesday, the day before the research went public. The provider patched its own fleet with a live patch, telling Droplet customers: "No action needed on your part."

Operators who run their own KVM hosts on AMD hardware need to update the host kernel or turn nested virtualization off. Oren Yomtov, a researcher at the security firm Terra Security, found the flaw and reported it through the provider's bug bounty program. The provider confirmed the exploit worked on its own hosts and treated it as critical.

In the test on one of its Droplets, the first thing to come back was the host's kernel version banner, followed by about 127 GB of the host's RAM, mapped read-only. The write test ran on the researchers' own bare-metal AMD server, with no other customers attached. There, the guest wrote 32 chosen bytes into a live page of the host kernel's memory.

An attacker would need root access inside a VM controlled by the researchers. 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 were not vulnerable because they had not enabled nested virtualization on AMD.

Technical Details

The flaw stems from a pointer left pointing at freed memory. KVM confines each VM with a nested page table that translates the VM's memory addresses into the host's real memory. When a reset signal called INIT stops the nested VM, KVM skips restoring the outer VM's pointer, leaving it pointing to a page of memory the kernel has already freed.

Once the kernel reused that freed page, the guest could fill it with entries of its own choosing. The forged entries could name any physical page on the host, which is how about 127 GB of the server's RAM came into reach of a guest that was never given it. The fix makes KVM reset that memory-management state on every INIT.

The flaw was created by a security fix. A 2022 patch for a different nested-virtualization bug, CVE-2022-3344, switched a reset path back to the outer VM's control block but missed the page-table pointer.

What to Do

The fix lives in the host kernel. Updating the operating systems inside the VMs changes nothing. Upstream, the fix shipped on Tuesday in stable kernel 7.3.5 and in the long-term kernels 6.18.64 and 6.12.118.

Distribution kernels mostly do not have the fix yet. As of publication, Debian's security tracker lists the kernels in all of its releases as vulnerable, and Ubuntu's CVE tracker rates the flaw High. Red Hat lists the Enterprise Linux 9 and 10 kernels as affected with the fix deferred.

Until a fixed host kernel is installed and the host rebooted, the only available protection is to turn nested virtualization off. To check and change it: run cat /sys/module/kvm_amd/parameters/nested. If the value is 1 or Y, add options kvm_amd nested=0 to the host's module configuration and reboot.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog