Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

AMD KVM Host-Memory Flaw Let Researcher Read 127 GB From a Cloud VM, Provider Confirms

DigitalOcean confirms a controlled demonstration of CVE-2026-99312 reading 127 GB of host RAM from a guest on AMD KVM with nested virtualization. Fixed Linux host kernels are available.

Newsroom editorial artwork
PUBLISHED

IPCRIME | November 21, 2026. A vulnerability in Linux Kernel-based Virtual Machine (KVM) broke a key isolation boundary on certain AMD hosts with nested virtualization enabled. DigitalOcean has confirmed that researcher Oren Yomtov of Terra Security accessed approximately 127 gigabytes of physical host memory from inside a test virtual machine in a controlled demonstration. A separate experiment on a bare-metal host also showed the ability to modify a small amount of host memory.

The issue is identified as CVE-2026-99312. This is a virtualization-host defect, not a routine vulnerability in an ordinary Linux website, nor a flaw that can be exploited simply by visiting an exposed HTTP page. The tested attack required privileged control inside a guest running on a vulnerable AMD KVM host with nested virtualization available.

What failed at the virtual-machine boundary

Nested virtualization allows a virtual machine to run another virtual machine. The affected KVM code did not properly reset the virtual CPU’s memory-management context when emulating an INIT processor reset in specific nested-guest conditions. The stale mapping could point to memory no longer belonging to the intended guest context. That opens a route for host-memory disclosure and, under the demonstration’s conditions, modification.

DigitalOcean says the proof-of-concept running on one of its Droplets exposed the physical host’s kernel banner and then about 127 GB of RAM. The researcher demonstrated a 32-byte write into a selected kernel-memory page only on a separate, controlled bare-metal AMD system without other customers. The public test is significant without inventing claims that production customers’ data was stolen.

What environments are actually at risk

Red Hat’s advisory specifies AMD-based KVM environments with nested SVM virtualization enabled. Intel-based KVM systems are not affected by this particular issue, and a standard AMD host without the vulnerable nested-virtualization path does not have the same exposure. A Linux desktop user whose system is only a guest cannot remediate an affected cloud provider’s hypervisor kernel by upgrading software inside that guest.

The prerequisite is also material: the reported testing began with root privileges within the researcher’s own guest virtual machine. It does not establish unauthenticated remote exploitation of a hypervisor from the public Internet.

Fixes and vendor-specific steps

The Linux kernel CVE announcement lists fixes in upstream 7.3.5, 6.18.64 and 6.12.118, and in development release 7.4-rc2. Operating-system vendors may backport corrections under different package versions, so confirm against the host distribution’s security bulletin rather than matching the major kernel number alone.

DigitalOcean says it deployed a live-patching response across its infrastructure, with no customer action required for its Droplets. Other operators maintaining their own affected AMD KVM hosts can update their host kernels and perform any required restart; where an upgrade cannot be deployed immediately, the provider identifies disabling nested virtualization through the kvm_amd module as a compensating step. That change can disrupt workloads that intentionally run nested virtual machines and belongs in planned maintenance.

Checklist for hosting operators

  • Inventory which physical KVM hypervisors use AMD processors and have nested virtualization enabled.
  • Identify affected host-kernel builds through the vendor’s security guidance and document which are already corrected.
  • Prioritize shared or untrusted-tenant hosts and review whether nested virtualization is actually required.
  • Apply the supported host-kernel correction and verify the running build; do not mistake a guest OS patch for a hypervisor fix.
  • Review telemetry and access boundaries if there is independent reason to suspect abuse, while recognizing that no real-world criminal campaign was established in the published research.

Source record

DigitalOcean — November 19 first-party disclosure and remediation; Linux kernel CVE announcement and fixed branches; Red Hat advisory — affected scope and conditions; IPCRIME CVE lookup.

Independent reporting based on documented testing; IPCRIME has not executed a cross-tenant proof of concept or reproduced any private host memory.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.

One response to “AMD KVM Host-Memory Flaw Let Researcher Read 127 GB From a Cloud VM, Provider Confirms”