# Linux KVM flaw CVE-2026-99312 lets guests reach host memory on AMD hosts with nested virtualization. What to patch

> A use-after-free in KVM's nested AMD (SVM) code let a root user in a test VM read about 127 GB of host RAM at DigitalOcean. Fixed kernels 7.3.5, 6.18.64 and 6.12.118 are out, but most distro packages are not yet, so AMD hosts that run nested VMs should patch and reboot, or turn nesting off.

Published Nov 21, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/linux-kvm-cve-2026-99312-amd-nested-virtualization-guest-reads-host-memory-what-to-patch

A Linux kernel bug tracked as **CVE-2026-99312** lets a virtual machine with root inside it read, and in some cases write, the host's memory on **AMD servers that have nested virtualization turned on**. The Hacker News reports that Terra Security researcher Oren Yomtov found it through DigitalOcean's bug bounty program. In DigitalOcean's test, a root user in a guest read about **127 GB of host RAM**. On the researchers' own bare-metal AMD server, they wrote **32 bytes into live host kernel memory**.

Why it matters: crossing from guest to host is the worst kind of bug for anyone renting out VMs or isolating untrusted workloads. The fix exists only in the kernel on the host, so updating guests does nothing. The kernel CVE record was published November 18, and according to The Hacker News the research went public November 18.

## What's wrong

According to the kernel's CVE text (mirrored by Tenable and ThreatInt), when KVM emulates an INIT signal while a nested (L2) guest is running with paging turned off, it can keep running the outer (L1) guest on a stale memory-management context. The Hacker News describes this in practice as a dangling pointer to a freed page-table root. The fix makes KVM reset the MMU context on every emulated INIT.

The kernel text says the bug **affects only nested SVM** (AMD). On Intel's VMX, INIT is always intercepted. The Hacker News reports that a 2022 fix for CVE-2022-3344 introduced the problem, so it sat in the kernel for almost four years.

## Key facts

| | Detail |
|---|---|
| Affected | x86 KVM hosts on AMD CPUs with nested virtualization enabled |
| Not affected | Intel KVM hosts (per kernel text and The Hacker News) |
| Attacker needs | Root inside a guest on a vulnerable host; network access alone is not enough |
| Kernel CNA score | CVSS 3.1 **8.8** (High) |
| Red Hat preliminary | Moderate, 5.6, denial of service only (per The Hacker News) |
| Fixed upstream | 7.3.5, 6.18.64, 6.12.118 (7.4-rc2 mainline) |
| Code introduced | 6.1 (2022), backported to 5.15.81 and 6.0.11 |
| Public exploit | None published, per The Hacker News |
| Exploited in the wild | No reports, per The Hacker News (citing VirtFusion) |

The two scores differ a lot. The kernel team's 8.8 assumes confidentiality, integrity and availability are all hit. Red Hat's preliminary rating treats it as denial of service only. The DigitalOcean memory read and the 32-byte write reported by the researchers suggest the higher reading is the realistic one for exposed hosts.

## Distro status

Fixed packages were patchy as of November 20–21:

- **Debian:** its tracker lists bookworm (6.1), trixie (6.12.117) and forky (7.3.4) as vulnerable. Only sid (7.3.5) is fixed.
- **Ubuntu:** rates it High, with no fixed package released yet, per The Hacker News.
- **Red Hat:** EL9 and EL10 affected with the fix deferred; EL8 not affected, per The Hacker News.
- ThreatInt's record lists the 6.1 line as affected with no fixed 6.1.y release named. We could not confirm a 5.15 or 6.1 stable fix, so check with your vendor.

DigitalOcean says it live-patched its fleet and that customers need to do nothing. The Hacker News adds that many cloud providers it surveyed were never vulnerable, because they had not enabled AMD nested virtualization.

## What to do

1. **Check whether you're exposed.** On each AMD KVM host, run:

   ```
   cat /sys/module/kvm_amd/parameters/nested
   ```

   `1` or `Y` means nesting is on. The Hacker News, citing VirtFusion, says it is on by default in kvm_amd.

2. **Patch and reboot the host** onto 7.3.5, 6.18.64, 6.12.118 or a vendor kernel that includes the fix, unless you have a live-patching service that covers it. Guests don't need updating.

3. **If you can't patch yet, turn nesting off.** Add this to a modprobe config file such as `/etc/modprobe.d/kvm.conf`, then reboot:

   ```
   options kvm_amd nested=0
   ```

   This breaks any tenant or workload that runs VMs inside VMs, such as CI runners, so warn them first.

4. **If you rent VMs rather than run hosts,** there is nothing to patch on your side. Ask your provider whether its AMD hosts had nested virtualization on and whether they are fixed.

Who should care most: hosting companies, VPS panels, private clouds and CI platforms on AMD EPYC hardware that let customers run their own VMs or nested hypervisors.


## Sources

1. [The Hacker News — Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts](https://thehackernews.com/2026/11/new-linux-kvm-flaw-cve-2026-99312-lets.html)
2. [Tenable — CVE-2026-99312](https://www.tenable.com/cve/CVE-2026-99312)
3. [Debian Security Tracker — CVE-2026-99312](https://security-tracker.debian.org/tracker/CVE-2026-99312)
4. [ThreatInt — CVE-2026-99312 record](https://cve.threatint.com/CVE/CVE-2026-99312)
