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-mitigation — Shell script that applies an interim nftables and sysctl mitigation for CVE-2026-98432 on Ubuntu, with check, self-test, apply, and remove commands. | Kitploit
Tools/GitHubGitHub/valkenindustries
/cve-2026-98432-mitigation
Defensive ToolsVulnerability AnalysisConfiguration AuditingNetwork SecurityMisconfigurationIncident Response
GitHubvalkenindustries/cve-2026-98432-mitigation

cve-2026-98432-mitigation

Shell script that applies an interim nftables and sysctl mitigation for CVE-2026-98432 on Ubuntu, with check, self-test, apply, and remove commands.

View Repository
516 days agoNot yet reviewed
Share

CVE-2026-98432 mitigation for Ubuntu

An interim mitigation for CVE-2026-98432, a use-after-free in the Linux kernel's IPv4 TCP code that affects kernels back to 4.4.

This does not patch your kernel. It makes the bug harder to reach until Ubuntu ships a fixed kernel. Install that kernel when it's available, then run remove. Check the current status on Ubuntu's CVE page.

Usage

sudo ./cve-2026-98432-mitigate.sh check       # report status, changes nothing
sudo ./cve-2026-98432-mitigate.sh self-test   # prove the rule works, in a temporary namespace
sudo ./cve-2026-98432-mitigate.sh apply       # apply the mitigation
sudo ./cve-2026-98432-mitigate.sh remove      # undo it, after installing a fixed kernel

Read the script before running it as root.

check exits with 0 if the host is fixed or mitigated, 1 if it is exposed, and 2 if it could not run.

What apply does

  1. Blocks the trigger. It adds an nftables rule that drops IPv4 TCP packets carrying IP options, before they reach the vulnerable code. Normal traffic very rarely uses IP options.
  2. Keeps the rule across reboots. It installs a small systemd service that loads the rule before the network starts. If that service fails, the host still boots, but without the rule.
  3. Disables MPTCP for new sockets. The publicly described remote code execution used an MPTCP listener. Use --keep-mptcp if the host really needs MPTCP.

It also installs the nftables package if it's missing.

It creates these files:

/etc/nftables-cve-2026-98432.nft
/etc/systemd/system/cve-2026-98432-nft.service
/etc/sysctl.d/90-cve-2026-98432-mptcp.conf

What you need to do yourself

Restart services that are listening on MPTCP. Existing sockets stay MPTCP until the service restarts. The script lists them but won't restart anything for you.

Go 1.24 and later enables MPTCP on listeners by default when the kernel supports it, so you may have MPTCP listeners you never chose. On older kernels ss -M won't show listeners, so check looks for tcp-ulp-mptcp in ss -tlni instead.

Limitations

  • The kernel stays vulnerable. This rule hasn't been tested against a real exploit, because none is public. Red Hat describes its similar rule as reducing exposure, not fully preventing it.
  • Containers: run this on the host, because containers share its kernel. Each new network namespace starts with MPTCP enabled, so containers need their own setting, such as docker run --sysctl net.mptcp.enabled=0. The firewall rule sees traffic entering through the host's network stack, but setups such as macvlan or ipvlan can bypass it.
  • Other firewall tools: anything that flushes the whole ruleset also removes this rule. The default /etc/nftables.conf starts with flush ruleset, so restarting or reloading nftables.service removes the rule until the next boot. Run check afterwards, or run apply again.
  • Fix detection: check looks for the CVE in the running kernel's Ubuntu changelog. If it isn't listed, the script treats the kernel as vulnerable, even if the fix arrived some other way.
  • Past compromise: this only protects from now on. It doesn't tell you whether a host has already been attacked.

Tested on

apply, check, self-test and remove were run in containers with the userland of Ubuntu 20.04, 22.04, 24.04 and 26.04, all on one 5.15 host kernel. Other kernels weren't tested.

Containers don't run systemd, so the script's service start and a real reboot weren't exercised. After you apply this, run self-test on your own system, and run check after your next reboot to confirm the rule came back.

References

  • Ubuntu CVE status
  • Upstream fix: "ipv4: free inet_opt and ireq_opt after an RCU grace period"

Credits

Special courtesy of Team Valken.

License

Public domain, under the Unlicense. No warranty: you run this at your own risk.

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.

    831
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    429
  • 4

    redforge

    cybersecurity91/redforge

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

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

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

    275

Explore all tools

Browse our collection of tools

View all tools →