← All security briefings

Attention

Linux KVM on AMD: CVE-2026-99312 conditional guest escape with nested virtualization

Identifiers: CVE-2026-99312

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

The Linux kernel CNA announced CVE-2026-99312 on November 18, 2026, and DigitalOcean published its original disclosure on November 19, 2026. The issue is in KVM nested SVM on AMD hosts with nested virtualization enabled, and vendor analysis assumes the attacker can act as root inside a guest on such a host. The CNA record lists the affected stable branches and names 6.12.118, 6.18.64 and 7.3.5 as example versions that carry the fix upstream.

Classification reason: Attention. Upstream stable fixes exist and the preconditions are specific; the issue matters mainly to those operating or renting KVM hosts on AMD hardware.

Impact

This is a hypervisor isolation issue. Under the described conditions a guest could reach host memory. Authorized research showed host-memory access on a DigitalOcean test account and demonstrated a write on isolated hardware. It is not a website service bug and does not make every guest VM vulnerable; the exposure sits at the host.

Who is affected

Applies to KVM hosts on AMD processors with nested virtualization enabled. Distribution status is separate from the upstream record. As of November 21, 2026, the Ubuntu CVE tracker lists the Noble linux package and the Jammy linux-aws-6.8 package as Vulnerable, with no fixed revision on those rows; other Ubuntu kernel variants must be checked individually on the tracker rather than inferred. Ubuntu users should not install raw upstream kernels.

Products and versions

Products and versionsAffectedFixed
Linux KVM host with AMD nested virtualization Affected upstream builds and distribution-specific backports per the Linux CNA and package tracker Upstream stable 6.12.118, 6.18.64 and 7.3.5 for the listed branches; distribution versions differ

Exploitation evidence

Exploitation not established. The reviewed sources report authorized research only. No confirmed real-world malicious exploitation is reported, and no source shows that specific tenants' information was leaked; this is not evidence that no misuse occurred.

Sources: DigitalOcean, Linux kernel CVE team

Actions

  1. If your site runs on a managed VM, follow your provider's guidance. DigitalOcean states its Droplet fleet received a live hypervisor fix and no customer action is needed for this CVE; this says nothing about other providers.
  2. If you operate the KVM host, apply the supported vendor kernel fix and verify that the running hypervisor includes it.
  3. If a vendor fix is not yet available, ask the platform admin to disable nested virtualization where this is compatible with the guests that depend on it.
  4. Do not treat a guest operating system update as a fix; only the host kernel fix addresses this.

Unknowns

  • Your provider, the host CPU architecture, and whether nested virtualization is enabled for your machine.
  • Whether the host has been misused historically.

Sources

  • Linux kernel CVE team · published · retrieved https://lists.openwall.net/linux-cve-announce/2026/11/18/2
  • DigitalOcean · retrieved https://www.digitalocean.com/blog/cve-2026-99312-kvm-patch
  • Canonical · retrieved https://ubuntu.com/security/CVE-2026-99312

Change history

  1. — Published: November 21, 2026: Published in English and Vietnamese, based on the Linux kernel CNA announcement of November 18, 2026, the DigitalOcean disclosure of November 19, 2026, and the Ubuntu CVE tracker as checked on November 21, 2026 as a distribution example.

Subscribe: RSS feed · JSON Feed · Feed format and fields