AnswersPublished24 sources
PwnEscape: The Linux Networking Bug That Put VM Isolation at Risk
PwnEscape (CVE 2026 99999) is rated CVSS 3.1 9.3 Critical: code inside a guest VM can exploit Linux packet processing logic to disclose host memory. The bug is in Linux’s shared networking stack, not in KVM itself: guest controlled checksum metadata can alter an IPv4 header after validation, causing fragmentation to...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer
Key takeaways
- PwnEscape (CVE 2026 99999) is rated CVSS 3.1 9.3 Critical: code inside a guest VM can exploit Linux packet processing logic to disclose host memory.
- The bug is in Linux’s shared networking stack, not in KVM itself: guest controlled checksum metadata can alter an IPv4 header after validation, causing fragmentation to copy beyond the packet data.
- The published stable fixes are 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, and 7.2.11.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: What is the critical, CVSS 9.3 Linux networking-stack vulnerability PwnEscape (CVE-2026-99999), how does guest-controlled virtio checksum-of. Article summary: PwnEscape (CVE-2026-99999) is reported as a critical, CVSS 3.1 9.3 Linux networking-stack vulnerability that can let code inside a guest VM cross the guest–host isolation boundary, disclose host memory, and potentially c. Topic tags: general, general web, user generated, education. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, cha
PwnEscape (CVE-2026-99999) is a critical Linux kernel vulnerability rated 9.3 under CVSS 3.1. It affects IPv4 packet processing: metadata supplied with a guest’s network traffic can cause the host kernel to change a packet header after validating it, then trust the changed header during fragmentation. The reported impact ranges from host-memory disclosure to a guest-to-host escape demonstrated in a lab. 4
8
23
How checksum metadata leads to an overread
Network devices can use checksum offload metadata to tell the kernel that checksum work remains to be completed. PwnEscape involves bad or untrusted metadata reaching the IPv4 stack: during checksum completion, the kernel can overwrite part of a header that has already been processed. The accepted fix adds a check on checksum_start before completing the checksum. 19
23
That creates a validation-and-use mismatch. Later, fragmentation code relies on the altered IPv4 header to determine how much header data to copy. In the reported test case, the header was treated as 60 bytes even though only 28 bytes of logical packet data were available. The 32-byte difference came from memory beyond the packet’s logical data boundary. That is a description of this test case, not a claim that every packet leaks exactly 32 bytes. 18
Why this is a VM-isolation problem
The flaw is in Linux’s networking stack rather than in KVM’s hypervisor code. That matters because a guest’s traffic can pass through the host kernel’s shared packet-processing path: fixing or replacing one hypervisor does not, by itself, address a vulnerability in that path. The relevant exposure is on hosts running an affected kernel that process attacker-controlled guest traffic through the vulnerable code. 3
8
The reported attack requires control of code inside a guest VM to send crafted packets; the available reporting does not describe it as an unauthenticated attack against any Linux machine reachable over the internet. 4
7
What researchers demonstrated
Reporting describes host-memory disclosure against Vercel production sandboxes. Separately, the researcher demonstrated host-level code execution in a lab environment. Those are distinct results: the available evidence does not establish root-level execution on Vercel’s production systems. 4
6
Paulos Yibelo found the issue while taking part in Vercel’s Sandbox security challenge. Reporting says the challenge received 1,285 submissions and describes PwnEscape as its sole critical finding. Those figures do not establish that customer data was accessed. 24
30
37
Fixes and what operators should check
The upstream fix is identified as commit 6785011f8b16, titled ipv4: validate checksum_start before completing checksum. Published stable releases containing the fix include 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, and 7.2.11. 12
27
Because the flaw is in the host kernel’s packet-processing path, operators should verify and update the host kernel—not rely on updating software inside guest VMs as a substitute. Distribution kernels may use different version numbers or release schedules, so check the relevant vendor advisory and confirm the host is running its patched kernel. 1
6
As of October 16, AlmaLinux reported that patched kernels were available. That is a dated status update, not a complete picture of every distribution’s rollout; availability can differ by vendor and release. 6
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "PwnEscape: The Linux Networking Bug That Put VM Isolation at Risk"?
PwnEscape (CVE 2026 99999) is rated CVSS 3.1 9.3 Critical: code inside a guest VM can exploit Linux packet processing logic to disclose host memory.
What are the key points to validate first?
PwnEscape (CVE 2026 99999) is rated CVSS 3.1 9.3 Critical: code inside a guest VM can exploit Linux packet processing logic to disclose host memory. The bug is in Linux’s shared networking stack, not in KVM itself: guest controlled checksum metadata can alter an IPv4 header after validation, causing fragmentation to copy beyond the packet data.
What should I do next in practice?
The published stable fixes are 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, and 7.2.11.
Sources
cyberstack.orgcyberstack.org · n · vercel-kvm-escape-20261003Vercel Sandbox (3 Oct): CEO confirms KVM zero-day guest→host root...
pwn.aiPwnEscape: Guest-to-Host KVM Escape (CVE-2026-99999) - pwn.ai
tenable.comCVE-2026-99999 | Tenable®
tuxcare.comPwnEscape Escapes the VM Without a Hypervisor Bug
qiita.comCVE-2026-99999（PwnEscape）を読み解く──「KVMの脆弱性」ではなく、L...