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_98432_guard — Temporary eBPF/XDP mitigation for CVE-2026-98432 Linux TCP IPv4 header-options vulnerability. Helps protect unpatched systems and custom kernels until an official kernel fix can be deployed. | Kitploit
Tools/GitHubGitHub/hdp1972be-svg/cve_2026_98432_guard
Defensive ToolsPacket Sniffing & AnalysisVulnerability AnalysisNetwork SecurityMisconfigurationIncident Response
GitHubhdp1972be-svg/cve_2026_98432_guard

cve_2026_98432_guard

Share

Temporary eBPF/XDP mitigation for CVE-2026-98432 Linux TCP IPv4 header-options vulnerability. Helps protect unpatched systems and custom kernels until an official kernel fix can be deployed.

View Repository
1715 days agoNot yet reviewed

CVE-2026-98432 — Temporary XDP Mitigation

Status: Temporary mitigation — not a permanent fix
Platform tested: Linux / Ubuntu 20.04 (should work upwards) Kernel tested: 5.15.0-124-generic (Expected to work on newer Linux kernels providing the required eBPF and generic XDP functionality. Compatibility must be verified on the target kernel.) Implementation: eBPF XDP, generic (SKB) mode
Date: 2026-11-03


1. Purpose

This project provides a temporary network-level mitigation for the IPv4/TCP attack surface associated with CVE-2026-98432.

The objective is to reduce exposure while a corrected kernel is being prepared, installed and deployed.

The mitigation rejects inbound IPv4 TCP packets containing IPv4 header options. It does this at the XDP ingress hook, before the packet reaches the normal IPv4 and TCP networking stack.

This is deliberately a narrow, fail-open mitigation:

  • Matching IPv4/TCP packets with IPv4 options are dropped.
  • Other traffic is passed normally.
  • Truncated or incomplete IPv4 headers are passed rather than indiscriminately discarded.
  • No TCP connection state is maintained.
  • No payload inspection or application-layer processing takes place.

This is not a kernel fix. It is a temporary measure intended to buy time until a corrected kernel has been compiled, installed and boot-tested.

2. Why this mitigation exists

The vulnerable attack surface is associated with handling IPv4 TCP traffic and IPv4 header options.

IPv4 header options are an uncommon feature in ordinary modern network traffic. They include mechanisms such as:

  • Record Route (RR)
  • Internet Timestamp
  • Loose Source Route
  • Strict Source Route
  • Router Alert
  • Other IPv4 option types

The IPv4 header contains a header-length field, IHL, expressed in 32-bit words.

A normal IPv4 header without options has:

IHL = 5 (20 bytes)

An IPv4 header containing options has:

IHL > 5 (more than 20 bytes)

The XDP program uses this distinction to reject IPv4 TCP packets with an extended IPv4 header.

This avoids passing that particular packet class into the kernel's normal TCP processing path.

3. How the XDP filter works

The program is attached to network interfaces using XDP generic mode.

Its processing sequence is:

  1. Read the Ethernet header.
  2. Recognise up to two VLAN headers.
  3. Identify IPv4 traffic.
  4. Check that the fixed IPv4 header is present.
  5. Check the IPv4 version and IHL.
  6. Check that the complete IPv4 header, including any declared options, is present.
  7. If the protocol is TCP and IHL > 5, drop the packet.
  8. Otherwise, pass the packet to the normal networking stack.

Simplified decision logic:

if (ether_type == IPv4) {
    if (ipv4_header_is_incomplete)
        PASS;

    if (ipv4_version != 4)
        PASS;

    if (ipv4_header_length_is_invalid)
        PASS;

    if (ipv4_protocol == TCP && ipv4_ihl > 5)
        DROP;
}

PASS;

The actual implementation also handles up to two VLAN tags.

XDP actions

ConditionAction
IPv4 TCP, IHL greater than 5DROP
IPv4 TCP, IHL equal to 5PASS
IPv4 UDPPASS
Other IPv4 protocolsPASS
IPv6PASS
Non-IP Ethernet trafficPASS
Incomplete/truncated IPv4 headerPASS

The implementation does not parse TCP options. TCP timestamps, SACK and window scaling are not IPv4 header options and remain unaffected.

3b. Why XDP instead of Netfilter or iptables?

This mitigation uses XDP (eXpress Data Path) rather than Netfilter/iptables because the objective is to discard matching packets as early as reasonably possible in the Linux networking receive path.

Packet processing position

With generic XDP (SKB mode), the filter runs at the ingress stage before the packet enters the normal network protocol stack and before Netfilter's usual IPv4 processing hooks.

This has several advantages for this particular mitigation:

  • Early rejection: IPv4 TCP packets containing IPv4 header options are discarded before normal IPv4 and TCP processing.
  • Reduced processing overhead: Dropped packets do not continue through subsequent networking layers, including the normal Netfilter processing path.
  • Narrow execution scope: The program only inspects Ethernet, optional VLAN headers and the relevant IPv4 header fields. It does not require connection tracking, NAT or firewall rule evaluation.
  • Predictable filtering logic: The decision is based on the IPv4 protocol field and IHL value, making the filter small and straightforward to audit.
  • Independent deployment: The mitigation is implemented as an eBPF program and does not require modifying existing iptables or nftables firewall rules.

Why not iptables or Netfilter?

iptables and nftables are perfectly valid ways to implement this same filtering rule. In fact, Netfilter-based filtering is a legitimate alternative and may be preferable where an administrator already manages ingress filtering centrally through the firewall.

However, those mechanisms operate later in the receive path than XDP generic mode.

For this specific use case, filtering before normal IPv4/TCP processing is desirable because the vulnerability concerns the handling of IPv4 TCP packets carrying IPv4 header options.

Generic XDP (SKB mode)

This project deliberately uses generic XDP rather than driver-specific native XDP.

Generic XDP operates on the SKB-based receive path and therefore provides broader compatibility with network drivers that do not implement native XDP support.

The trade-off is that generic XDP does not provide the same early execution point or performance characteristics as native driver-mode XDP. It should not be confused with hardware-offloaded XDP.

Design decision

The choice of XDP is not based on the assumption that Netfilter is insecure or unsuitable.

It is based on placing this particular packet filter as early as practical in the Linux receive path, while retaining broad compatibility through generic XDP.

The objective is to reject the relevant packet class before it reaches the vulnerable IPv4/TCP processing path, not to replace the host firewall.

4. What this mitigation blocks

The filter blocks all IPv4 TCP packets carrying IPv4 header options, not just Record Route.

This includes packets containing, for example:

  • Record Route
  • IPv4 Timestamp
  • Loose Source Route
  • Strict Source Route
  • Router Alert, when carried in an IPv4 TCP packet
  • Other IPv4 options

The filter does not distinguish between individual IPv4 option types. It rejects the entire IPv4 TCP packet whenever the IPv4 header length exceeds 20 bytes.

This is intentional: a broad and simple rule is preferable to an incomplete option-type blacklist for this temporary mitigation.

5. What it does NOT block

This mitigation has deliberately limited scope.

It does not:

  • Fix the vulnerable kernel code.
  • Protect interfaces on which the XDP program is not attached.
  • Filter IPv4 TCP packets arriving through paths that bypass the attached ingress hooks.
  • Filter loopback traffic.
  • Filter IPv6 traffic.
  • Filter IPv4 UDP or other non-TCP protocols.
  • Reject normal IPv4 TCP packets with a 20-byte IPv4 header.
  • Inspect TCP options.
  • Inspect TCP payloads.
  • Detect or prevent unrelated kernel vulnerabilities.
  • Replace a kernel security update.

It also does not perform general IP packet validation. Incomplete or malformed packets outside the specific checks implemented by the program may still be passed to the kernel.

Do not interpret a successful XDP deployment as proof that the host is no longer vulnerable.

6. Statistics

The program uses a per-CPU array map:

cve_2026_98432_stats

Map properties:

  • Type: percpu_array
  • Key size: 4 bytes
  • Value size: 8 bytes
  • Maximum entries: 2

Counters:

KeyMeaning
0IPv4 TCP packets with IPv4 options dropped
1Incomplete/truncated IPv4 headers passed
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →