A serious security vulnerability in the Linux Kernel-based Virtual Machine (KVM) has raised concerns about the security of virtualized environments running on AMD processors.

The vulnerability, tracked as CVE-2026-99312, affects AMD systems using nested virtualization.

Security researcher Oren Yomtov of Terra Security demonstrated that the flaw could allow a guest virtual machine to read sensitive memory belonging to its host system.

In testing, the researcher reportedly accessed approximately 127 GB of host RAM from a DigitalOcean guest environment.


Key technical details


  • CVE ID: CVE-2026-99312
  • Affected technology: Linux KVM
  • Affected hardware: AMD-based systems
  • Attack type: Host memory disclosure
  • Affected configuration: Nested virtualization enabled
  • Researcher: Oren Yomtov, Terra Security


How does the vulnerability work?


  1. An attacker obtains access to a guest virtual machine.
  2. The attacker exploits a flaw in the KVM virtualization implementation.
  3. The vulnerability can expose memory belonging to the host system.
  4. Sensitive information stored in host memory could potentially be accessed.
  5. This creates risks for cloud providers and organisations running multiple virtual machines on shared infrastructure.


Why is this vulnerability dangerous?


  • Cloud security risks: Sensitive host memory could be exposed.
  • Data confidentiality: Information belonging to other workloads may be at risk.
  • Virtualization security: The isolation between guest and host environments could be weakened.
  • Enterprise infrastructure: Organisations using AMD-based virtualized servers may face additional security risks.



  • Update Linux kernels to patched versions.
  • Disable nested virtualization if it is not required.
  • Monitor virtual machine activity for suspicious behaviour.
  • Review AMD-based virtualization infrastructure.
  • Apply security updates from Linux distributions as they become available.


Patch information: Fixes were included in Linux kernel versions 7.3.5, 6.18.64 and 6.12.118. Distribution-specific updates should also be checked.

Canadian Cyber Security Journal