PwnEscape Linux Flaw Threatens Cloud VM Isolation

PwnEscape, a critical Linux kernel flaw, exposes host memory and can enable VM escape under certain conditions. Fixes are available.
A critical Linux kernel vulnerability known as PwnEscape could allow an attacker running code inside a virtual machine to disclose memory belonging to the host system and, under certain conditions, escape the virtual machine entirely.
Tracked as CVE-2026-99999, the vulnerability affects Linux networking code used in certain virtualisation environments. It has received a reported severity score of 9.3 out of 10, placing it in the critical category.
Security researcher Paulos Yibelo of pwn.ai discovered the flaw while participating in a security challenge organized by cloud platform provider Vercel. The research demonstrated that specially crafted network packets originating inside a virtual machine could expose host memory.
The researcher also demonstrated host crashes and a full guest-to-host escape in a controlled laboratory environment. However, the host-memory disclosure was the part demonstrated against Vercel’s production sandboxes. The more advanced exploitation was not established as a compromise of Vercel’s production infrastructure. No real-world exploitation had been reported in the sources reviewed.
PwnEscape originates in the Linux kernel’s networking code, where improper validation of packet checksum metadata can allow a deferred checksum operation to modify part of an IPv4 header after the kernel has already processed it.
In practical terms, an attacker who can execute code inside an affected virtual machine may be able to send specially crafted network packets that trigger the vulnerability.
The researcher demonstrated that the resulting packet-handling error could expose approximately 32 bytes of host memory in a single disclosure. Repeating the process could expose additional data.
The same underlying flaw also provided the basis for more advanced exploitation. In a controlled test environment, the researcher demonstrated host crashes and eventually achieved code execution on the host with administrator-level privileges.
These outcomes represent different stages of exploitation. A memory disclosure does not automatically provide control of a host, and the laboratory demonstration should not be interpreted as proof that an attacker has achieved host-level access in a production cloud environment.
Virtual machines are widely used to isolate applications and workloads running on shared physical infrastructure. Cloud providers and other hosting operators rely on these isolation boundaries to prevent one customer’s workload from accessing another customer’s data or the underlying host.
PwnEscape is concerning because the flaw exists in the Linux kernel’s networking code rather than in a single cloud provider’s application or a specific hypervisor implementation.
The documented vulnerability is particularly relevant to certain KVM-based virtualisation hosts using the affected networking path, including configurations involving virtio-net and TAP. An attacker must already be able to execute code inside a guest environment, so the vulnerability does not simply allow an unauthenticated outsider to take over any Linux server over the internet.
The potential consequences depend on the host’s configuration, kernel version and available attack paths. In vulnerable environments, a successful guest-to-host escape could undermine the isolation protecting other workloads on the same machine.
However, it would be inaccurate to conclude that every Linux-based cloud service is affected.
AWS has explicitly stated that its managed compute and container services, including Amazon EC2, AWS Lambda and AWS Fargate, are not affected by this issue. Its advisory instead identifies certain self-managed KVM virtualisation configurations running unpatched kernels as requiring attention.
The vulnerability was discovered during a security challenge announced by Vercel on August 18, 2026. The programme offered a total prize pool of up to $1 million for researchers who could break out of the company’s sandbox environment.
Yibelo reported finding the initial memory-disclosure issue within three days. The investigation subsequently developed into a demonstration of guest-to-host code execution on researcher-controlled systems.
According to the researcher’s account, the work involved AI-assisted source-code analysis combined with human direction, testing and validation. The researcher used an experimental research system designed to maintain context across extended investigations and test possible attack paths.
Vercel’s final programme results identified PwnEscape as its sole critical finding. The vulnerability was traced to the Linux kernel rather than a misconfiguration unique to Vercel’s infrastructure.
The finding illustrates how a weakness in a foundational operating-system component can undermine security controls built around it, even when the surrounding virtualisation environment has been carefully hardened.
A fix for PwnEscape has been incorporated into the Linux kernel and backported to multiple stable branches.
The reported upstream fixed versions are:
- Linux 5.10.272
- Linux 5.15.223
- Linux 6.1.190
- Linux 6.6.159
- Linux 6.12.113
- Linux 6.18.57
- Linux 7.2.11
These are upstream kernel version references, not a universal list of package versions for every Linux distribution. Distributions may backport the fix into their own supported kernels without using the exact version number shown above.
The upstream change adds validation to prevent the checksum operation from writing into the IPv4 header in the affected code paths. Its author described it as a defence-in-depth measure, noting that broader validation work was still needed.
Administrators should therefore consult their operating system vendor’s security advisory to determine whether their installed kernel contains the fix.
Administrators responsible for self-managed virtualisation infrastructure should establish whether their systems use the affected networking configuration and whether the host kernel has been patched.
The immediate priorities are:
- Update affected host kernels using the appropriate distribution or vendor security package.
- Reboot where necessary to ensure the system is running the updated kernel.
- Verify that the fix is present on every relevant virtualisation host, rather than checking guest operating systems alone.
- Follow specific advisories from cloud and infrastructure providers for their own environments.
Updating only the kernel inside a virtual machine does not fix a vulnerable host kernel. The underlying host must be addressed separately.
AWS has published its own remediation guidance for affected self-managed KVM environments running Amazon Linux. For other distributions, administrators should follow the relevant vendor’s instructions. AWS says there is no workaround for the affected configurations that replaces applying the fix.
PwnEscape demonstrates how a vulnerability in a host operating system’s networking stack can threaten the isolation that virtual machines are designed to provide.
The confirmed production finding was host-memory disclosure in Vercel’s sandboxes. Host crashes and full guest-to-host code execution were demonstrated in the researcher’s controlled environment, and should not be presented as confirmed production compromises.
The flaw is not a universal remote takeover vulnerability, nor does its existence mean that every cloud service running Linux is exposed. Its relevance depends on the specific virtualisation setup, host kernel and available attack path.
Nevertheless, the reported severity and demonstrated potential to cross a virtual-machine boundary make PwnEscape an important issue for operators of affected infrastructure. With fixes available, administrators should verify their exposure and apply the appropriate security updates.
Source: The Hacker News
References in this story
- Issue in the Linux kernel virtio-net/TAP networking path affecting KVM-based hypervisors aws.amazon.com
- Critical PwnEscape Linux Kernel Vulnerability Lets Guest VMs Read Host Memory thehackernews.com A critical Linux kernel flaw let a guest VM read host memory in Vercel's live sandboxes; host code execution was shown only in lab tests.



