Technology1 min read

Virtualization, Responsible Disclosure, and CVE-2026-99312

By · Published by Everything Blog

In short

The vulnerability originated nearly four years ago when an incomplete security patch left a stale pointer during nested CPU resets. In laboratory testing on an isolated bare-metal AMD machine, researchers confirmed the danger by reading 127 GB of physical host RAM and altering live kernel memory. Following a coordinated disclosure via a bug bounty program, maintainers pushed upstream updates across multiple stable kernel branches. Cloud infrastructure has since applied live patches to safeguard customer environments without enforcing server reboots.

Key points

  • Attackers with root access to a nested virtual machine could compromise multi-tenant data…: Attackers with root access to a nested virtual machine could compromise multi-tenant data on host systems.
  • Upstream Linux kernel fixes were tagged on November 9 and released across versions 7.3.5,…: Upstream Linux kernel fixes were tagged on November 9 and released across versions 7.3.5, 6.18.64, and 6.12.118 on November 17.
  • Live kernel patches deployed across Droplet infrastructure fully mitigated the risk witho…: Live kernel patches deployed across Droplet infrastructure fully mitigated the risk without requiring customer action.

Sources checked by our analysis pipeline: 1

By Tyler Healy

Every cloud customer gets the same promise: a bright-line boundary between your workload and your neighbors. Your virtual machine is yours, your neighbors’ are theirs, and the hypervisor keeps it that way.

A hypervisor is large, complex software written by people, and flaws come with that. These boundaries get tested to fix those flaws. What matters is who finds them first and what they do next.

A researcher who finds a flaw in shared infrastructure can publish it, sell it, or tell us. Responsible disclosure partners tell us – that gives open source maintainers who own the code time to build and test a fix before an attacker can use it. It is the difference between a quiet patch cycle and an all-hands emergency.

The gap between a flaw going public and attackers using it is now near-zero, or ahead of patch in some cases. Early notice is how we stay ahead of the issues that could break the day-to-day businesses running on the cloud. We would rather hear about a problem from a partner than from…

Technology