KVM flaw lets AMD guests escape to the host (CVE-2026-99312)
Original title: CVE-2026-99312: KVM Guest-to-Host Escape
Researchers read about 127 GB of host RAM from a DigitalOcean droplet; a host write was shown only on their own server.
Researchers say a use-after-free in Linux KVM, CVE-2026-99312, lets a guest with root escape to the host on AMD CPUs with nested virtualization enabled. The bug leaves a nested page-table pointer aimed at a freed page after an INIT exit, and has been in the kernel for just under four years. On a DigitalOcean droplet they demonstrated reading host memory; on their own bare-metal AMD server they wrote 32 chosen bytes into a live host kernel page. The published excerpt does not name a fix.
Unconfirmed: No patch is named in the excerpt, and host memory writes were shown only on the researchers' own server.
- Only a guest VM and root inside it were required.
- The race worked on 6 of 12 boots on a large droplet.
- A cloud host gives one real attempt per boot, the researchers say.
- The write primitive was not demonstrated on DigitalOcean.
- Arbitrary host write is described as the basis for code execution.
Impact: Guest read and write of host memory, including other tenants
| Product | Affected |
|---|---|
| Linux KVM | AMD CPUs with nested virtualization; present for just under four years |
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-99312 | Stale KVM MMU context on nested SVM INIT | — | — |
From the original article
8 min read at terra.security
Rent a server in the cloud and one thing comes with the bill: you are alone in there. Your VM is yours, your neighbors' VMs are theirs, and the hypervisor keeps it that way. We broke that boundary on an ordinary DigitalOcean droplet , and reached the physical host and every other tenant's VM on it.
By Kozmik1 · terra.security
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.