Linux KVM flaw let a guest VM read 127 GB of host memory — AMD hosts only
A flaw in KVM, the hypervisor built into the Linux kernel, let a guest virtual machine read and write the memory of its physical host — demonstrated on a DigitalOcean Droplet, where the first thing returned was the host's kernel version banner, followed by about 127 GB of host RAM.
📊 Scorecard: our Bearish call on $AMD is scored from $424.39, the last close before it ran. Its first result comes after the next close.

The News
A flaw in KVM — the hypervisor built into the Linux kernel, the core of the operating system — let a guest virtual machine read and write the memory of its physical host. A hypervisor is the software that lets one physical computer run many virtual machines, each believing it has its own hardware. The promise at the heart of cloud computing is that those virtual machines cannot see each other. This flaw broke that promise. Terra Security researcher Oren Yomtov demonstrated it on a DigitalOcean Droplet, a rented cloud server: the first thing returned was the host's kernel version banner, followed by about 127 GB of the host's RAM mapped read-only.
The write test was even more alarming, and it was done carefully. On his own bare-metal AMD server — a physical machine he owned, with no other customers attached — Yomtov wrote 32 chosen bytes into a live page of the host kernel. On a shared host, that memory can include other customers' virtual machines, which is why the read alone is so serious: a tenant reading 127 GB of host memory could be reading another customer's data. The bug, CVE-2026-99312, affects only hosts with AMD processors and nested virtualization enabled — a setting that lets a virtual machine run its own virtual machines inside it. Intel hosts are unaffected.
The flaw has a long backstory. It was caused by a stale nested-page-table pointer — a reference to a map of memory that was left pointing at memory that had already been freed — after an INIT reset, and it was introduced by a 2022 fix for a different nested-virtualization bug (CVE-2022-3344). It sat in the kernel for just under four years. Yomtov reported it through DigitalOcean's bug bounty program — a system that pays researchers for reporting flaws — and to the Linux KVM maintainers on Oct. 21. The fix was merged on Nov. 2, shipped in stable kernels 7.3.5, 6.18.64 and 6.12.118 on Nov. 17, and the CVE was published on Nov. 18. DigitalOcean reproduced the exploit on its own hosts, treated it as critical, live-patched its fleet, and told Droplet customers: "No action needed on your part."
One guest VM reading 127 GB of its host's memory breaks the promise cloud computing is built on.
Why It Matters
The core issue is isolation, and isolation is the product cloud providers sell. When you rent a virtual machine, you are trusting that the provider's hypervisor keeps your data separate from every other tenant on the same physical host. A flaw that lets one guest read 127 GB of host memory breaks that trust at the deepest level — not through a misconfigured setting or a stolen password, but through the virtualization layer itself. That is why DigitalOcean treated it as critical and patched its entire fleet without waiting for customers to act.
The severity disagreement is a real one, and it is reported here rather than reconciled. The Linux kernel's CVE team scores the flaw 8.8 out of 10 — a high severity, reflecting the read and write access to host memory. Red Hat first assessed it at 5.6, rating it as denial-of-service only — a flaw that can crash a system rather than steal from it — and has since raised the score to 7.8 (Important). The two scores reflect different judgments about how exploitable the flaw is in practice, and until there is more evidence, both stand. What is not in dispute is that the demonstration worked, twice, on real systems.
The four-year lifetime of the flaw is its own lesson. It was introduced by a fix for a different bug, which means the code that created it was itself a security improvement. That is a pattern security engineers know well: fixes can introduce new flaws, and flaws in low-level code like a hypervisor can sit quietly for years because so few people read that code closely. The fix is now shipped, but operators running their own KVM hosts on AMD hardware must update the host kernel or turn nested virtualization off — DigitalOcean's customers are covered, but self-hosted operators are on their own.
Analyst's Take
Our call is Bearish. A hypervisor flaw that lets a guest virtual machine read a host's memory is a worst-case scenario for cloud infrastructure, and the fact that it sat in the kernel for just under four years before a researcher found it will worry anyone who rents cloud servers. AMD is the hardware read-through, since only AMD hosts with nested virtualization are affected, and DigitalOcean is the operator read-through — though its fast fleet patch is the one genuinely good part of the story.
What to watch next is whether any real-world exploitation emerges. So far there is none reported — the demonstrations were by a researcher, one on a rented Droplet and one on his own server — but the flaw was public from Nov. 18, and the window between disclosure and patching is when exploitation usually starts. Operators who have not yet updated their host kernels should treat the Nov. 17 fixed kernels as the deadline that matters.
For cloud customers, the practical takeaway is narrow and reassuring: if you rent from DigitalOcean, the company says no action is needed on your part. If you run your own KVM hosts on AMD hardware, the action is yours to take. Reader poll: Do you run AMD hosts with nested virtualization — yes or no? Vote: Yes, patched, Yes, not yet, No AMD hosts.
Are you bullish or bearish on this story?
By The Numbers
FAQ
What is a hypervisor?
A hypervisor is software that lets one physical computer run many virtual machines at the same time, sharing its processor, memory and storage between them. KVM is the hypervisor built into Linux, the operating system that powers most of the world's servers. If the hypervisor has a flaw, the separation between virtual machines can break down.
What is a virtual machine?
A virtual machine, or VM, is a software-defined computer that runs inside a physical computer, with its own operating system and applications. Cloud providers rent VMs to customers — a DigitalOcean Droplet is one — and many VMs share a single physical host. Each VM is supposed to be isolated from the others.
What is nested virtualization?
Nested virtualization is a setting that lets a virtual machine run its own virtual machines inside it — virtualization within virtualization. It is useful for testing and development, but it adds complexity, and this flaw only affects hosts where it is enabled. Turning it off removes the risk.
What is a kernel?
The kernel is the core of an operating system — the part that manages the processor, memory and hardware directly. KVM is built into the Linux kernel, which is why a flaw there is so serious: it sits at the lowest level of the system, underneath everything else.
👁
Source: The Hacker News