Linux Kernel VM Escape CVE-2026-99999 and Cloud Provider Response

TL;DR

---

A critical vulnerability with a CVSS base score of 9.3 (NIST), designated CVE-2026-99999 and dubbed PwnEscape, has been disclosed in the Linux kernel networking stack.
Because the flaw allows guest virtual machines to compromise the underlying host operating system via KVM escapes, cloud providers and web hosting operators are evaluating their infrastructure exposure.
In Japan, Sakura Internet issued an emergency security notice on October 16, 2026, and froze new signups for its VPS offerings as well as shared hosting services.

How IPv4 Checksum Miscalculations Enable Guest Escapes

In virtualized architectures such as public clouds and VPS environments, multiple guest virtual machines share a single physical host.
Hypervisors typically enforce strict separation between guest instances, but this flaw enables an adversary to break through virtualization barriers and target host resources.

The issue originates from improper validation of checksum offsets in the kernel’s IPv4 networking code.
Specifically, insufficient bounds checking on the checksum_start metadata inside packet buffers causes the kernel helper function skb_checksum_help() to write data outside allocated buffer boundaries.

Researchers at security firm pwn.ai demonstrated that sending crafted IPv4 packets from an isolated KVM guest can leak host kernel memory and crash the physical node.
By pairing out-of-bounds corruption with targeted memory feng-shui, the researchers achieved arbitrary code execution with root privileges on the hypervisor host.
While in-the-wild exploitation has not been observed, direct corruption of host kernel memory from unprivileged guest boundaries is an immediate risk.
Unlike the earlier NVIDIA Container Toolkit vulnerability CVE-2024-0132, which exploited file system mappings to escape container isolation, CVE-2026-99999 uses standard network packet handling as its breakout vector.

Sakura Internet Suspends New Signups Across All Hosting Tiers

On October 16, 2026, Sakura Internet published an advisory detailing its response to CVE-2026-99999.
To facilitate security reviews and apply protective measures, the provider halted new applications for all Sakura VPS tiers, shared hosting plans, and managed dedicated servers.
Project provisioning in Sakura Cloud was also paused.
Existing active servers continue normal operations, though future scheduled host maintenance may be required.

While Sakura Internet did not elaborate on specific operational factors, the signup suspension is a safeguard against malicious actors provisioning fresh instances to launch breakout attacks against neighboring tenants.
On VPS and cloud platforms, tenants have root control and can send custom raw packets or load specialized kernels. This makes them potential targets for exploit attempts.
In contrast, as noted in our guide on reproducing Japanese hosting environments with Docker, shared hosting tenants lack root access and cannot directly craft low-level network packets.
Suspending shared hosting alongside VPS plans reflects a priority on verifying hypervisor isolation across all shared clusters.

Provider Status and Administrator Action Items

As of October 16, 2026, other major Japanese hosting providers—including Xserver, ConoHa, and Lolipop—have not announced intake suspensions comparable to Sakura Internet.
Because this vulnerability resides in the host operating system kernel, required actions depend on your hosting deployment model:

Hosting Model	Examples	Impact and Required Action
Shared Web Hosting	Sakura Rental Server, Xserver, Lolipop	The hosting provider manages the hypervisor and OS. End users have no maintenance steps to run and should review operator maintenance schedules.
Managed VPS / Cloud	Sakura VPS, ConoHa VPS, Sakura Cloud	The provider secures the virtualization host. Updating the guest VM kernel alone does not remediate hypervisor exposure; monitor provider maintenance announcements.
Dedicated / Bare Metal	Sakura Dedicated Server PHY, bare-metal hardware	Administrators manage their own operating systems. Check official security bulletins from your OS distribution, install updated kernel packages, and reboot.

Note that updating the kernel inside a guest VM or VPS container does not remediate the vulnerability on the underlying hypervisor. This update step applies strictly to environments where you directly manage the host OS or physical bare-metal hardware.
For administrators who manage self-hosted environments like the setup covered in our ConoHa VPS configuration guide, updates can be installed directly through standard package managers.
On Ubuntu systems, run sudo apt update && sudo apt --only-upgrade install linux-image-generic. On AlmaLinux or Rocky Linux, execute sudo dnf update kernel and reboot the machine to load the patched kernel.