Threat advisory: Linux KVM guest-to-host memory exposure, CVE-2026-99312

Published 20 November 2026, 9 pages, Mitigata Threat Research

In plain words

Someone who already had full control of one virtual computer could read about 127 gigabytes of the real computer's memory in a test. DigitalOcean has fixed its own servers, so its customers need to do nothing. Companies that run their own servers should install the fix and restart, or turn the risky setting off.

For business leaders

A flaw in Linux KVM on AMD hosts with nested virtualization let a researcher with root inside one virtual machine read about 127 GB of host memory. Red Hat rates it Moderate, and no attacks on other customers are confirmed. On a shared host, other tenants' data could sit in that memory, which the source calls an impact scenario rather than a breach. Installing the fixed kernel changes nothing until it is activated by live patch or reboot. Ask three things this week: which hosts run AMD with nested virtualization, whether the fixed kernel is active, and whether the vendor has confirmed its backport. A confirmed incident must be reported to CERT-In within 6 hours under Section 70B.

For security analysts

Technique: guest-to-host memory disclosure via a stale nested-page-table pointer. During emulated INIT in nested virtualization, KVM may fail to reset the MMU context, letting a guest reach host physical memory. Attacker needs root inside a guest on an AMD host with nested virtualization enabled. Not unauthenticated remote exploitation. Intel KVM and AMD hosts without nested virtualization are not affected by this path. Exploit status: authorised research demonstrations only; no confirmed attacks on other customers; public proof of concept not stated. Research read the host kernel version and about 127 GB of host RAM, read-only, from a DigitalOcean Droplet. Separately, 32 chosen bytes were written to a live host kernel page on a bare-metal AMD research server. Red Hat CVSS 5.6, Moderate. Step 1, patch: install vendor-fixed host kernel 6.12.118, 6.18.64, 7.3.5 or later, or 7.4-rc2; vendor backport status not stated. Step 2, activate: live patch or host reboot; installing alone does not change the running kernel. Step 3, verify: check running kernel version. Step 4, interim if unpatched: kvm_amd nested=0 via change control; guests relying on nested VMs will be affected. Guest OS updates do not remediate. Step 5, detect: AMD hosts with nested virtualization enabled; host kernels older than the fixed builds; unusual activity on shared hosts if compromise is suspected. Specific indicators not stated.

Key points

CVE ids covered: CVE-2026-99312

The full report is a PDF that opens with a work email.