Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-99999 — Go probe that reproduces the Linux IPv4 checksum-offload bug PwnEscape on a prepared TAP, injecting crafted virtio headers and verifying the out-of-bounds fragment header copy. | Kitploit
Tools/GitHubGitHub/perongh/cve-2026-99999
Packet Sniffing & AnalysisVulnerability AnalysisExploitationNetwork SecurityLabs & Practice
GitHubperongh/cve-2026-99999

CVE-2026-99999

Go probe that reproduces the Linux IPv4 checksum-offload bug PwnEscape on a prepared TAP, injecting crafted virtio headers and verifying the out-of-bounds fragment header copy.

View Repository
22341 month agoReviewed by Kitploit
Share

CVE-2026-99999 lab probe

Go probe for the Linux IPv4 checksum-offload bug known as PwnEscape. It attaches to a TAP you already prepared and checks whether the host fragmenter trusts an IPv4 header rewritten by skb_checksum_help.

The probe handles packet injection and capture. scripts/setup.sh prepares the lab interfaces, sysctl settings, and nftables rule inside the pwnesc network namespace. scripts/teardown.sh removes the lab.

What it checks

On a kernel that still completes a partial checksum before reading ihl (reproduced here on 6.18.54; fixed in 6.18.57):

  1. A virtio checksum header with csum_start=22 is accepted. Two VID-0 tags are then stripped (14+4+4), so the checksum write lands on the IPv4 version/IHL byte.
  2. The first byte changes from 0x45 to 0x4f. The fragmenter uses a 60-byte header.
  3. With conntrack defrag and the default -head 8, the linear head is 28 bytes, so the 60-byte header copy reads 32 bytes past skb_headlen into the output fragments' IPv4 options.

This exercises the disclosure primitive described in PWN.AI's PwnEscape write-up. With CONFIG_INIT_ON_ALLOC_DEFAULT_ON, fresh slab tailroom may appear as zeroes in the copied bytes.

Prerequisites

  • A Linux test host or VM with a kernel that completes partial checksums before reading ihl
  • Go 1.27.1 or newer
  • Root privileges for lab setup and the probe
  • ip, nft, sysctl
  • Built-in or loadable nf_conntrack and nf_defrag_ipv4
  • /dev/net/tun

Build and run

From the repository directory on the host:

go build -o poc .
sudo ./scripts/setup.sh
sudo ip netns exec pwnesc ./poc

The probe opens pwntap with IFF_TAP|IFF_NO_PI|IFF_VNET_HDR and captures output on pwnv1. Reserve pwntap for the probe. The nftables ct rule activates conntrack defragmentation, and pwnv0 uses MTU 200 to fragment the reassembled datagram again on output.

A successful header check prints verify: first byte 0x4f ihl=15. The probe then reports the output fragments, their IPv4 options, and the bytes copied past the linear head.

Options

  • -head (default 8): offset-0 fragment payload in bytes; a multiple of 8 from 8 through 40. The expected copy past the linear head is 40 - head bytes.
  • -rest (default 400): completing-fragment payload in bytes; at least 16.
  • -spray (default 0): number of same-sized frames allocated immediately before the offset-0 fragment.
  • -spray-fill (default 0xee): byte used to fill those frames.
  • -page: use a page_frag head, whose tail can contain skb metadata. The default is a slab head.
  • -skip-verify: go directly to the fragmented-datagram check.

PWN_TAP selects the TAP interface (default pwntap). PWN_CAP selects the capture interface (default pwnv1). The setup script uses these default names.

Cleanup

After the probe finishes, exit any shells in pwnesc and run from the host:

sudo ./scripts/teardown.sh

This deletes pwnesc along with its interfaces, ip pwn nftables table, and namespace-local sysctl settings.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →