Skip to content
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report
FrameFrame home

Your digital life. Back in your hands.

100% Canadian-owned · Support: support@frameprivacy.com

Product

  • Platform
  • Sample report
  • Breach Check
  • Frame agent
  • Extension
  • Mobile app
  • Pricing
  • Frame Business
  • Changelog

Resources

  • Blog
  • Help centre
  • Free leak test
  • Status
  • Data-broker catalog
  • RSS feed

Company

  • About
  • Our privacy promise
  • Contact
  • Press and brand

Legal

  • Legal hub
  • Privacy Policy
  • Terms
  • Security
  • Cookies
  • Accessibility

© 2026 Frame Labs Inc. All rights reserved.

en Englishfr Français
Your Privacy ChoicesSystem status

All posts

Research · 4 min read

A researcher read 127 GB of a cloud server’s memory from inside a rented virtual machine

Terra Security found a four-year-old bug in Linux KVM on AMD servers with nested virtualization. DigitalOcean has patched its fleet; people who run their own KVM hosts need a kernel update.

BBy Brody · FramePublished November 20, 2026
A memory chip icon in a cyan circle inside dotted rings, with small cloud and stacked layers icons around it, on a dark background.

When you rent a virtual machine in the cloud, it usually shares a physical server with other customers. The hypervisor, the software that runs all those machines, is supposed to keep each one walled off. On November 18, 2026, Oren Yomtov of Terra Security published research showing a way through that wall in KVM, the hypervisor built into Linux.

From inside a DigitalOcean Droplet, he was able to read about 127 GB of the physical host’s memory. On a shared host, that memory includes other customers’ virtual machines. The bug is tracked as CVE-2026-99312 and is already fixed.

Who is affected

Only KVM hosts with AMD processors and nested virtualization turned on (the feature that lets a virtual machine run virtual machines of its own). Terra says many cloud providers it surveyed were not vulnerable because they don’t enable nested virtualization on AMD.

  • DigitalOcean customers: DigitalOcean says it validated the exploit, built a live patch and rolled it across its fleet. “No action needed on your part.”
  • Anyone running their own KVM hosts on AMD: you need to update the host kernel, or turn nested virtualization off.

You would need root access inside your own virtual machine to use this. It is not something a website or app can do to your laptop.

What the researcher demonstrated

Terra separates what it proved where:

  • On DigitalOcean: reading, not writing. The forged mapping covered about 127 GB of host memory, read-only, and the first thing found was the host’s kernel version banner, as proof it was really host memory.
  • On Terra’s own bare-metal AMD server, with no other customers: writing. The virtual machine put chosen bytes (32 of them, per DigitalOcean) into a page of the host’s kernel memory, confirmed by a test module loaded on the host.

Terra deliberately did not test writing on shared infrastructure. Neither Terra nor DigitalOcean reports anyone else using the bug.

How it works, in plain terms

Every virtual machine’s memory addresses have to be translated into real addresses on the host, using a table that KVM keeps in protected memory. The processor finds that table through a single pointer.

When a virtual machine runs its own nested virtual machine and that nested machine is stopped by a reset signal called INIT, KVM forgot to update the pointer. It kept pointing at a page that had already been freed. When the host reused that page for something else, the attacker’s virtual machine could arrange for the processor to read a page the attacker controlled as part of the translation table. From there, the researcher could write his own table and point it at any host memory.

A fix that made a bug

The flaw sat in Linux for just under four years. It was introduced by the 2022 fix for an earlier KVM bug, CVE-2022-3344. Terra notes that in its separate “PatchSlop” research, 3.2% of kernel CVEs were introduced by the fix for another CVE. DigitalOcean’s takeaway: “Fixes deserve the same scrutiny as the code they patch.”

Timeline

  • October 21, 2026: reported to the Linux KVM maintainers, after first going through DigitalOcean’s bug bounty program.
  • November 2: fix merged into the main Linux kernel; first tagged in 7.4-rc2 on November 9.
  • November 17: released in stable kernel 7.3.5 and long-term kernels 6.18.64 and 6.12.118.
  • November 18: CVE published and research released.

What to do if you run KVM on AMD

  1. Update the host kernel to 7.3.5, 6.18.64, 6.12.118 or later (or your distribution’s kernel that includes the fix).
  2. If you can’t update yet, set the nested parameter of the kvm_amd module to 0. That disables nested virtualization and closes this path completely.
  3. If you only rent virtual machines, check your provider’s notices. Most people don’t need to do anything.

Related coverage

  • Researchers showed a hostile host can read data inside AMD confidential VMs: the opposite direction, where the host is the attacker and the virtual machine is the target.

Sources

  • Terra Security (Oren Yomtov), CVE-2026-99312: KVM Guest-to-Host Escape, November 18, 2026
  • DigitalOcean (Tyler Healy), Virtualization, Responsible Disclosure, and CVE-2026-99312, November 19, 2026
More in Research

More stories

  • Research“FastUnlock”: someone holding your locked Windows 11 PC can run programs through Narrator, with no fix yetNovember 20, 2026 · 3 min read
  • ResearchResearchers planted fake keys in public container images. Bots used the first one in 8 secondsNovember 19, 2026 · 4 min read
  • MalwareSpies behind EggStreme rebuilt their malware within weeks of being exposed, Bitdefender saysNovember 19, 2026 · 4 min read

New posts, by email.

About once a month. Plain-language privacy notes, nothing else. I never share your address.

Sent by Frame · privacy@frameprivacy.com · Privacy Policy

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report