Illustration of an open navy server with a memory chip, a violet box holding a smaller box and a magenta magnifying glass looking at the memory

KVM Flaw on AMD Hosts: What to Check If Your Site Is on a VPS

Admin

A flaw in KVM, the Linux virtualization technology behind many VPS plans, let a virtual machine read the physical server's memory on AMD hosts with nested virtualization enabled. It was disclosed on November 18, 2026 as CVE-2026-99312, and fixed kernel versions are already out.

What we know

  • What it is: according to Terra Security's analysis published on November 18, the bug sits in KVM's code for AMD processors and only shows up when the host has nested virtualization (virtual machines inside virtual machines) turned on. According to DigitalOcean and VirtFusion, exploiting it requires root inside a virtual machine on that host.
  • What was shown: Terra says that from a DigitalOcean Droplet it could see about 127 GB of the host's memory, read-only. DigitalOcean confirms this in its November 19 notice.
  • Who is not affected: according to Red Hat, Intel processors are not affected. Neither are AMD hosts with nested virtualization turned off.
  • Where it came from: Terra and DigitalOcean link it to the fix for an earlier 2022 flaw (CVE-2022-3344); DigitalOcean says that fix repaired one problem and missed this one.
  • The fix: the change landed in the mainline kernel on November 2 and in stable versions 7.3.5, 6.18.64 and 6.12.118, released on November 17, according to Terra, DigitalOcean and Debian.
  • What is still missing: VirtFusion, which makes software for VPS providers, says in its guide that the 5.15, 6.1 and 6.6 branches do not have a fixed release yet.
  • Severity: Red Hat rates it «moderate» (CVSS 5.6, preliminary). Ubuntu gives it medium priority and its kernel packages are still under evaluation. Debian listed its stable releases (bookworm and trixie) as vulnerable when this article was written.
  • What DigitalOcean did: it received the report through its bug bounty, validated it, prepared a live patch it is rolling out across its servers and tells Droplet customers no action is needed.
  • Attacks: VirtFusion says there is no public exploit and no known attacks. None of the other sources reports attacks.

What changes and what doesn't

The job falls on VPS providers and on anyone running their own AMD virtualization host: update the host kernel and reboot, or turn nested virtualization off.

Nothing changes inside your virtual machine. The flaw is in the physical server, not in your WordPress, your Drupal or your VPS operating system. Updating your VPS is good practice, but it does not fix this.

How to tell if it affects you

It depends on where your site lives:

  1. Shared hosting: you don't manage any virtualization host. If you want, ask your provider whether its servers run KVM on AMD and whether the fix is applied. Nothing changes on your site.
  2. VPS with a provider: the patch is theirs to apply. Ask: «Do your AMD hosts have nested virtualization enabled? When will you apply the fix for CVE-2026-99312?». Ask for a date. If you use DigitalOcean, its notice says no action is needed on your part.
  3. Your own KVM server on AMD (for example, Proxmox or libvirt): check the file /sys/module/kvm_amd/parameters/nested. If it says 1 or Y, nested virtualization is on.
  4. If it is on and you don't need it, the guides from Terra, DigitalOcean and VirtFusion say to turn it off with the nested=0 option of the kvm_amd module and reboot. VirtFusion warns it cannot be changed while virtual machines are running.
  5. Update the host kernel to 7.3.5, 6.18.64, 6.12.118 or your distribution's fixed package as soon as it ships, then reboot: the new kernel does not protect you until you do.
  6. Review your site's secrets: if your provider does not confirm the patch, it's a good time to know how you would rotate your database passwords and your site's API keys.

Related: Critical LXD and MicroCloud Flaw: What to Check Now

Sources

Updates: if Ubuntu, Debian or Red Hat ship fixed packages, or fixed releases appear for the 5.15, 6.1 and 6.6 branches, they will be added here with a link.

Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.