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
Tools/GitHubGitHub/datacenter-metrotel/mitigating-cve-2026-98432
Defensive ToolsVulnerability AnalysisScripting & AutomationConfiguration AuditingNetwork SecurityMisconfigurationIncident Response
GitHub
Share
datacenter-metrotel/mitigating-cve-2026-98432

Mitigating-CVE-2026-98432

Shell scripts that diagnose and mitigate CVE-2026-98432 on Linux: detect MPTCP state, check kernel patch level, disable MPTCP, and optionally block IPv4 TCP options via nftables.

View Repository
15 days agoNot yet reviewed

mptcp-check

Scripts to diagnose and mitigate CVE-2026-98432 on Linux servers: a use-after-free in the kernel's IPv4 TCP handshake. The scripts check whether MPTCP (Multipath TCP) is active, whether it is enabled by default or was enabled by someone, whether there are processes listening with MPTCP, and whether the kernel in use already has the patch, and depending on the scenario they propose a plan stating what they are going to do.

ScriptFor
mptcp-check-rhel.shRHEL, CentOS, Rocky, AlmaLinux, Oracle Linux, Fedora
mptcp-check-debian.shDebian, Ubuntu and derivatives (Mint, Pop!_OS, Kali, Raspberry Pi OS…)

The real solution is to install the fixed kernel. Turning off MPTCP reduces the attack surface of the known exploit, but it does not fix the bug: Red Hat states that an exposed TCP service is enough to trigger the race condition, and CIQ expressly warns that MPTCP alone should not be disabled.

About the vulnerability

  • CVE: CVE-2026-98432, race condition in the code that establishes new IPv4 TCP connections (use-after-free). IPv6 is not affected.
  • Since when: the bug has existed since Linux 4.4.
  • Severity: 9.8 according to the kernel CVE team; between 5.9 and 8.1 according to Red Hat, Oracle, SUSE and Amazon (they consider the complexity high).
  • Known exploit: Anthropic published that its model wrote an exploit that allows executing commands as root against servers with an MPTCP listener.
  • Upstream kernels with the fix: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3.

Fuentes:

  • The Hacker News: Linux Kernel TCP Flaw With 9.8 CVSS Score (29/10/2026, actualizado el 30/10)
  • CIQ: Mitigating CVE-2026-98432 on Rocky Linux (actualizado el 3/11/2026)
  • RFF: Red Hat has fixed kernels, Ubuntu's are in -proposed (actualizado el 3/11/2026)

Patch status (as of 11/3/2026, according to those sources)

It may be outdated: always verify in your distribution's security advisory.

DistributionStatus
RHEL 9Fixed kernel 5.14.0-687.64.1.el9_8 (RHSA-2026:93412), published on 11/1 according to RFF
Rocky 9RFF saw it on a Rocky 9.8 on 11/3; CIQ published fixed kernels for its commercial variants. For the community one, check Rocky's errata
Debian trixie and bookwormFixed (linux 6.12.113-1; bookworm also 6.1.190-1)
Oracle Linux 7–10 (UEK), SUSE Micro 6.2 / Leap 16.0, Amazon Linux 2023 (kernel6.18, kernel6.12)Fixed
UbuntuThe title of the RFF article indicates that the patches are in -proposed
RHEL 7Not affected

Is MPTCP enabled by default?

It depends on the distribution, and that is why the scripts do not assume it: they detect it.

  • RHEL and clones: according to Red Hat's documentation, MPTCP is compiled but disabled by default (net.mptcp.enabled=0) and must be enabled with a sysctl file. (From memory; confirm it with sysctl net.mptcp.enabled.)
  • Debian and Ubuntu: they follow the kernel default, which is usually enabled (1). On an Ubuntu 24.04 where I tested the script it appeared as 1.

Usage

chmod +x mptcp-check-rhel.sh mptcp-check-debian.sh

./mptcp-check-rhel.sh                  # diagnostica y propone un plan (no cambia nada)
sudo ./mptcp-check-rhel.sh --apply     # aplica los pasos automáticos, pidiendo confirmación
sudo ./mptcp-check-rhel.sh --apply --yes        # sin preguntar
sudo ./mptcp-check-rhel.sh --apply --with-nft   # además crea la regla de red (ver abajo)
sudo ./mptcp-check-rhel.sh --remove-nft         # quita la regla de red

(The same applies to mptcp-check-debian.sh.)

Scenarios and what the script does in each one

If the kernel in use already has the patch (according to its changelog), the script says so and exits without proposing anything: there is no need to mitigate. If it does not have it, or it could not be determined, it distinguishes three scenarios:

ScenarioWhenWhat it proposes
A. MPTCP offDisabled (by default or by configuration) or the kernel does not include itDoes not touch MPTCP: it adds nothing. Recommends updating the kernel and, if that cannot be done right away, the network rule (--with-nft).
B. MPTCP active, no listenersnet.mptcp.enabled=1 but nobody is listening with MPTCPWith --apply: sets net.mptcp.enabled=0 at runtime and persists it in /etc/sysctl.d/90-disable-mptcp.conf, so that new services (e.g. programs in Go 1.24+) do not open MPTCP listeners.
C. There are MPTCP listenersProcesses listening with MPTCP or services forced with mptcpizeThe same as B, and it also lists the services to restart. It does not restart them for you: open sockets remain MPTCP until they are restarted.

In all cases the last step, manual, is to install the fixed kernel and reboot. The script never updates the kernel or restarts anything.

In the diagnosis it also indicates why MPTCP is in that state: "enabled by default", "enabled by configuration (someone activated it)", "disabled by default" or "disabled by configuration", and it shows the sysctl files that define it.

Optional network rule (--with-nft)

This is the temporary mitigation proposed by CIQ and RFF for the bug itself, not just for MPTCP: an nftables table that drops IPv4 TCP packets with IP options.

  • It is created in the ip cve_2026_98432 table and saved to /etc/cve-2026-98432-block-ip-options.nft.
  • If systemd is present, a service is installed so that it survives a reboot.
  • Risks: it drops legitimate traffic with IP options (networks with CIPSO / NetLabel are an exception) and disappears if nftables is stopped or reloaded. Test it first on a non-production host.
  • Remove it with --remove-nft after installing the fixed kernel.

Exit codes

CodeMeaning
0The kernel in use appears to have the patch, or is not affected by version (earlier than 4.4)
1The kernel appears unpatched (or it could not be determined): there are recommended actions
2Usage error, permissions or unsupported system

Kubernetes

A Kubernetes worker shares the kernel with its containers, so the node's kernel is what matters. Kubernetes does not use MPTCP by itself, but components written in Go (kubelet, kube-proxy, containerd, etc.) could open MPTCP listeners if the kernel allows it and they were compiled with Go 1.24 or later. To update node by node: cordon, drain, update the kernel, reboot and uncordon.

Limitations

  • The patch and version checks are heuristic. The patch check looks for the CVE in the changelog of the kernel in use; the version check infers that kernels earlier than 4.4 do not have the affected code. They do not replace your distribution's security advisory.
  • Turning off MPTCP can affect applications that use it on purpose. Run the diagnostic mode first and review which services use it.
  • If another sysctl file enables MPTCP and is loaded after 90-disable-mptcp.conf, it would be re-enabled on reboot. The script warns about this when it detects conflicting files.
  • Unsupported systems (RHEL/CentOS 5 and 6, for example) do not have this bug due to their kernel version, but they accumulate other unpatched vulnerabilities.

Test status

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.

    962
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    558
  • 3

    redforge

    cybersecurity91/redforge

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

    348
  • 4

    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.

    344
  • 5

    ARTEX

    baarai/artex

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

    324
  • 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.

    297

Explore all tools

Browse our collection of tools

View all tools →