News / Sysadmin / KVM vulnerability: a VM read 127…
Sysadmin · Vulnerability

KVM vulnerability: a VM read 127 GB of host RAM

A KVM vulnerability let a guest VM read its AMD host's memory. Who's exposed, how to check for nested virtualization, and what to do until a fix ships.

opnF.shNov 20, 20265 min readkvm vulnerabilitycve-2026-99312nested virtualization
On this page 4 sections ▾

TL;DR

  • Debian, Ubuntu and Red Hat hadn't shipped fixed kernels as of November 20, so on those distros the fix for now is switching nested virtualization off.
  • Most cloud customers don't need to act: DigitalOcean live-patched its fleet, and many providers never had nested virtualization on for AMD.
New to this?Ping explains the hardest part in plain words.
CVE-2026-99312
Linux KVM (kvm_amd, nested virtualization on AMD)
HIGH8.8
Affected
AMD hosts with nested virtualization on, running kernels with the 2022 change (6.1 and later, plus 5.15.81 and 6.0.11 onward) that lack the fix
Fixed in
Linux 7.3.5, 6.18.64 and 6.12.118
Disclosed
Nov 18, 2026
Exploited
No known attacks and no public exploit code
Workaround
Set the kvm_amd nested parameter to 0 and reboot

Terra Security's Oren Yomtov had root inside a DigitalOcean Droplet and used it to read about 127 GB of the host server's memory. On a shared host, that memory holds other customers' virtual machines. The KVM vulnerability behind it, CVE-2026-99312, only works on AMD hosts with nested virtualization switched on, which KVM's AMD module does by default.

Quick facts

The first thing that came back from the host was its kernel version banner, text that should never be visible from inside a guest.

On a bare-metal AMD server with no other customers on it, Terra also wrote 32 chosen bytes into a live host kernel page.

The bug came from a 2022 fix for a different KVM flaw, CVE-2022-3344, and sat in the kernel for just under four years.

#How the KVM vulnerability works

Nested virtualization lets a virtual machine run virtual machines of its own. To keep every guest in its lane, KVM gives each one a page table that translates the guest's memory addresses into physical addresses on the host. The bug shows up when a virtual CPU inside a nested VM is reset. At that moment KVM should refresh the virtual CPU's pointer to the guest's page table. It didn't, so in DigitalOcean's words the pointer "kept naming a page KVM had already freed."

ELI5: explain it simply
Ping explainsNo experience needed.
THE WORDS
Nested virtualization
Running a virtual machine inside another virtual machine.
Page table
A lookup table that tells the computer which physical memory each address points to.
Use-after-free
A bug where a program keeps using memory after it has handed that memory back.
THE IDEA

Picture a hotel that gives each guest a map of which rooms are theirs. After a fire drill, the front desk forgets to hand one guest a fresh map, so they're still holding an old one that the hotel has since recycled. Whoever controls what's printed on that recycled map can send the guest into any room in the building.

That's a use-after-free. Once the freed page is handed out again, an attacker in the guest can fill it with page table entries of their own, and Red Hat says those forged entries give read and write access to host memory.

#Two scores for the same bug

The Linux kernel's CVE team scores CVE-2026-99312 at 8.8, with high impact on confidentiality, integrity and availability. Red Hat's preliminary score is 5.6, "Moderate," which counts the damage as denial of service only, even though its own write-up of the bug (covered above) says it gives read and write access to host memory. The researchers demonstrated both the read and the write, so if you triage by your distro's rating alone, this one is easy to underrate.

#Is your KVM host affected by CVE-2026-99312?

Three things have to be true: an AMD CPU, a kernel without the fix, and nested virtualization on. These commands check all three. Here's the output from our test machine, which is Intel:

check a KVM host
student@opnf:~$ lscpu | grep -i 'vendor id'
Vendor ID:                               GenuineIntel
student@opnf:~$ uname -r
6.18.44-fc-v726
student@opnf:~$ cat /sys/module/kvm_amd/parameters/nested
cat: /sys/module/kvm_amd/parameters/nested: No such file or directory

On an AMD host the last command prints 1 or Y when nested virtualization is on. Our kernel, 6.18.44, is older than the fixed 6.18.64, but this machine isn't exposed: it's Intel, so the AMD module isn't even loaded. The CPU rules a host in or out before the version number does.

If your host is AMD with nested on, here's where fixed kernels stood on November 20:

SystemStatus
Upstream LinuxFixed in 7.3.5, 6.18.64 and 6.12.118
DebianListed as vulnerable, fix only in unstable
UbuntuRated High, listed as vulnerable, no fixed package yet
Red Hat Enterprise Linux 9 and 10Fix deferred
Red Hat Enterprise Linux 8Not affected
Intel KVM hostsNot affected

If your host is exposed

Either get onto a fixed kernel or switch nested virtualization off until you can:

  1. Update the host kernel, then rebootMove to 7.3.5, 6.18.64 or 6.12.118 (or later in those series), or your distro's fixed package once it ships. The fix only takes effect after the host reboots into the new kernel, unless you use a live-patching service. On any other kernel series, use the next step for now.
  2. No fix yet? Turn nested offAdd options kvm_amd nested=0 to a file in /etc/modprobe.d/ and reboot. The reboot is needed because the setting can't change while VMs are running. Any guest that runs VMs of its own loses that ability until you turn nested back on.
  3. Check it tookAfter the reboot, cat /sys/module/kvm_amd/parameters/nested should print 0 or N.

DigitalOcean says setting the nested parameter to 0 "closes this path completely," so turning it off fully protects a host while you wait for a kernel.

Signs someone already tried

There's nothing to hunt for yet. No attacks have been reported outside the research, no exploit code has been published, and there are no published indicators of compromise. To use the flaw, an attacker has to control a VM on the host, and network access alone isn't enough (both demos started from root inside the VM). That puts the hosts that rent or hand out VMs to other people at most risk: VPS providers, private clouds and shared lab servers.

#Cloud VMs are probably fine, homelabs might not be

DigitalOcean patched its fleet with a live patch, which fixes the running kernel without rebooting the servers, and tells Droplet customers "No action needed on your part."

Many other providers weren't exposed in the first place, because nested virtualization was off on their AMD hosts.

The hosts left exposed are the ones people run themselves, and that includes homelabs. Proxmox VE runs on KVM, so a Proxmox box on a Ryzen or EPYC CPU is in scope until its kernel is updated, unless someone already turned nested off. If you built one from our homelab projects guide, run the three checks above on it.

Checking a kernel module's settings, changing them safely and rebooting a host without breaking what runs on it is server administration. The DevOps Pro ProCourse covers it in its Server Administration level, hands-on in a simulated terminal in your browser.

Are Intel KVM hosts affected by CVE-2026-99312?
No, even with nested virtualization on. The broken code is only in KVM's AMD module, kvm_amd.
Do I need to do anything for a DigitalOcean Droplet?
No. DigitalOcean live-patched its hypervisors, so the fix is on its side.
Can someone use this from outside a VM?
No. The attacker has to be running code inside a VM on the vulnerable host first, so a network scan or a website can't trigger it.

What this means for you

On any AMD KVM host, check cat /sys/module/kvm_amd/parameters/nested. If it's on, move to a fixed kernel and reboot, or set nested to 0 until your distro ships one.

Get opnF in your inbox

Tech news for IT professionals that actually teaches you something.

Our promise to you: we'll be conscious about email quality/frequency, and your address will never be shared/sold.