Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.
On November 17, 2026, the Linux kernel received a fix for CVE-2026-99312, a vulnerability in the KVM subsystem that allows a virtual machine with root privileges to access the host's physical memory. The bug affects only the AMD SVM implementation with nested virtualization enabled. Terra Security researchers demonstrated reading approximately 127 GB of host RAM from a DigitalOcean Droplet and writing 32 bytes into an active host kernel page on a bare-metal AMD server. The source does not specify whether this memory access constitutes a full VM escape.
- The vulnerability is a use-after-free in the KVM-AMD nested page table (NPT) pointer, triggered when INIT reset emulation leaves a stale pointer to already-freed memory.
- Researchers demonstrated reading ~127 GB of host RAM on DigitalOcean and writing 32 bytes into the host kernel on bare-metal AMD, both requiring root access to the guest VM. These figures come from DigitalOcean's disclosure as the sole structured primary source.
- The bug was introduced by the fix for CVE-2022-3344 in 2022 and remained in the code for roughly four years, manifesting only with nested virtualization enabled.
- DigitalOcean deployed a live patch requiring no customer action, but the kernels of major Linux distributions — Debian, Ubuntu, RHEL 9/10 — had not released patched packages as of November 20–21, 2026.
How It Works: INIT, NPT, and the Forgotten Pointer
The technical mechanism resides in KVM's handling of nested virtual machines. When a guest OS runs its own hypervisor (L1 hosts L2), the AMD processor uses Nested Page Tables (NPT) to translate L2 memory addresses into host physical addresses. Emulation of the INIT instruction, which resets the virtual processor, represents a critical point in this flow.
According to the kernel commit message, the problem arises because when INIT is emulated with paging disabled in the nested guest, KVM fails to restore the outer VM's (L1) NPT pointer. The pointer remains directed at a memory page the kernel has already marked as free. That page is then reallocated, the guest populates it with forged page tables, and the physical processor follows those addresses to access any region of host memory.
The fix, commit c7c288d178cb0b78d3464a616b16b1aa0b316049, changes the reset behavior unconditionally: every INIT now restores the MMU context, eliminating the inconsistency window. As the commit notes, the condition is impossible on Intel architecture: "INIT is an unconditional intercept on VMX, meaning it is impossible to emulate INIT while L2 is running." This architectural distinction limits the vulnerability to AMD systems with nested SVM only.
The Demonstrations on DigitalOcean and Bare-Metal
Oren Yomtov of Terra Security discovered the flaw, reporting it through DigitalOcean's bug bounty program. The cloud provider independently verified the exploit on its own hosts and classified the vulnerability as critical. The official disclosure describes two distinct demonstrations.
"The first thing that came back was the host kernel version banner. Then came about 127 GB of host RAM, read-only" — DigitalOcean on the read demonstration
In the first, executed on a DigitalOcean Droplet, researchers mapped approximately 127 GB of host physical memory read-only, starting with the host kernel version banner. In the second, on a researcher-owned bare-metal AMD server, a guest VM wrote 32 chosen bytes into an active host kernel memory page; a witness module loaded in the host kernel confirmed the modification. Both operations required root access to the researcher-controlled virtual machine.
DigitalOcean informed customers that "no action is required on your part," having deployed a live patch across its entire fleet without requiring instance reboots.
A 2022 Patch That Sowed a 2026 Bug: The PatchSlop Case
The genesis of CVE-2026-99312 falls into a phenomenon Terra Security has dubbed PatchSlop: security fixes that themselves introduce new vulnerabilities. In 2022, the patch for CVE-2022-3344 — a denial-of-service vulnerability in nested virtualization — modified the reset path toward the outer VM control block but omitted updating the page table pointer. The error remained in the code for roughly four years, invisible until nested virtualization conditions exposed the faulty path.
PatchSlop research data indicates that approximately 3.2% of kernel CVEs were introduced by fixes for other CVEs. The source does not specify the systemic scope of this phenomenon beyond the statistical observation.
The CVSS Scoring Disagreement
Severity scoring for CVE-2026-99312 has produced divergence among scoring authorities. The Linux kernel CNA assigned CVSS 3.1 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), rating the flaw HIGH. Red Hat initially scored it 5.6 Moderate, limiting impact to denial of service, then revised to 7.8 Important. This disagreement reflects differing interpretations of impact scope: the kernel CNA considers a scope change (S:C) for compromise of other VMs on the same host, while Red Hat's initial assessment did not include this dimension.
What to Do Now
- Verify architecture and configuration: confirm whether infrastructure uses AMD processors with the kvm_amd module and nested virtualization enabled; Intel systems and AMD hosts without nested virtualization are not vulnerable.
- Apply the patched kernel: the upstream fix is available in stable versions 7.3.5, 6.18.64, and 6.12.118; self-hosted operators must update the host kernel and reboot, interrupting all running VMs.
- Disable nested virtualization if not needed: the kvm_amd module enables nested virtualization by default; on self-managed hosts where it is unnecessary, disabling it removes the attack path.
- Monitor distribution vendors: as of November 20–21, 2026, Debian bookworm/trixie, Ubuntu, and RHEL 9/10 had not released patched packages; administrators must verify the status of their distributions.
Disclosure Context and Limits
The quantitative demonstrations — 127 GB of read access on DigitalOcean and 32 bytes of write access on bare-metal — come exclusively from DigitalOcean's disclosure, the cloud provider that coordinated the vulnerability through its bug bounty program. The source does not specify whether other cloud providers with similar configurations were affected. No exploit code has been published and no in-the-wild exploitation has been reported; the EPSS score remains below 1%.
The CVE record publication date on cve.org is November 18, 2026, while the upstream fix was published on November 17, 2026. Commit c7c288d178cb0b78d3464a616b16b1aa0b316049 is available in the official kernel repositories.
Sources
- thehackernews.com
- access.redhat.com
- digitalocean.com
- app.opencve.io
- sqmagazine.co.uk
- news.lavx.hu
- nvd.nist.gov
- cve.org
- security-tracker.debian.org
- ubuntu.com
- docs.virtfusion.com
Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.