A Four-Year-Old KVM Bug Lets a Cloud VM Read the Whole Host's Memory

CVE-2026-99312: KVM Guest-to-Host Escape

Terra Security escaped a DigitalOcean droplet and reached the physical host, reading roughly 127 GB of host RAM and, on their own bare-metal AMD server, writing 32 chosen bytes into a live host kernel page. The flaw lives in KVM on AMD CPUs with nested virtualization: an INIT reset skips the pointer refresh, leaving a use-after-free that the researchers turn into a forged page table. Ironically, a 2022 security fix opened it, and it sat in the kernel for nearly four years.

That 2022 fix has now needed at least two follow-on fixes, and one of them is this escape.
  1. immibis2

    Links to a CVE record. The kernel project marks everything that could conceivably be of any use to an attacker as a CVE. What are we actually looking at here? Sounds like a dangling-pointer type of bug?

  2. fwsgonzo

    Don't disable nested, it's still better security than everything else, and having it on means access to real hardware virtualization. Second, the article is AI-written. It really should be rewritten by a human.

  3. gerdesj

    404

  4. jacobgold

    Our infrastructure will become so much more secure but we're in for a bumpy ride through 2027.

  5. arde

    That's a 404 now.

  6. praseodym

    The blog post is very difficult to read, I suspect that unfortunately it’s fully written by an LLM.

  7. gbrindisi

    Thinking about agents sandboxes... it truly seems like the time is ripe for unikernels

  8. sadkgasjdfgk

    I wonder if AWS' Nitro Sandboxes would prevent this?

More from this day

2026-11-18