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-validation-mitigation — Read-only patch-state and exposure check for CVE-2026-98432 (Linux kernel IPv4 TCP use-after-free, CVSS 9.8), with opt-in interim mitigation and exact rollback. | Kitploit
Tools/GitHubGitHub/akamai/cve-2026-98432-validation-mitigation
Defensive ToolsVulnerability AnalysisScripting & AutomationConfiguration AuditingNetwork SecurityMisconfigurationIncident Response
GitHub
Share
akamai/cve-2026-98432-validation-mitigation

cve-2026-98432-validation-mitigation

Read-only patch-state and exposure check for CVE-2026-98432 (Linux kernel IPv4 TCP use-after-free, CVSS 9.8), with opt-in interim mitigation and exact rollback.

View Repository
91619 days agoNot yet reviewed

Check, mitigate, rollback

Patch-state and exposure check for CVE-2026-98432 (Linux kernel, IPv4 TCP, CVSS 9.8), with opt-in interim mitigation and exact rollback. The default mode is read-only. The script never triggers the vulnerability. It changes system state only with --mitigate or --rollback and records changes so it can be undone.

Requirements

  • Linux target, bash 3.2 or newer. Works unprivileged for the read-only check; package changelog and firewall counter reads may need root for complete results.
  • --mitigate and --rollback need root, plus nft (preferred) or iptables with the xt_u32 module for the firewall rule.
  • Optional: ss for listener counts, netlabelctl for the CIPSO guard, bpftool for XDP detection, systemctl for persistence.
  • The --kernel-version flag lets you exercise the version logic on any OS, including macOS.

Usage

./cve-2026-98432.sh                       # human-readable check
./cve-2026-98432.sh --json                # one JSON object, for diffing before/after
./cve-2026-98432.sh --kernel-version 6.12.112   # evaluate a version string instead of uname -r

sudo ./cve-2026-98432.sh --mitigate --dry-run
sudo ./cve-2026-98432.sh --mitigate [--disable-mptcp] [--persist] [--ignore-netlabel]
sudo ./cve-2026-98432.sh --rollback [--dry-run]
./cve-2026-98432.sh --help
FlagEffect
--jsonMachine-readable output. Warnings still go to stderr.
--kernel-version VRun the version logic against V. Skips all host probes.
--mitigateApply interim mitigations (see below). Refuses if a previous run is still recorded.
--disable-mptcpWith --mitigate: also set net.mptcp.enabled=0. Breaks apps that need MPTCP.
--persistWith --mitigate: make the changes survive reboot and firewall reloads.
--ignore-netlabelWith --mitigate: install the drop rule even when CIPSO labelled networking is configured.
--rollbackUndo a previous --mitigate exactly, then re-run the check.
--dry-runPrint the commands and file contents that would be used; change nothing.

--mitigate and --rollback are mutually exclusive. After either one the check runs again and prints the new state.

Exit codes

CodeMeaning
0PATCHED or NOT_AFFECTED
1VULNERABLE or LIKELY_VULNERABLE
2Usage error, missing root, Linux-only mode on another OS, or re-apply without rollback
3UNKNOWN patch state
4--mitigate or --rollback did not complete. The errors are on stderr and the report still shows the patch state.

Codes 0, 1 and 3 reflect patch state, never mitigation state. A mitigated but unpatched host still exits 1, because the mitigation is not a fix. Code 4 takes precedence, so automation can tell that a requested change failed even on a patched host.

How the verdict is reached

Checks run in this order and the first match wins:

  1. Package changelog mentions the CVE → PATCHED. Debian/Ubuntu: the installed linux-image-$(uname -r) changelog. RPM systems: rpm -q --changelog on kernel-core, kernel, kernel-default or kernel-uek. This is the only reliable signal for vendor kernels, which backport fixes without changing the upstream version.
  2. Upstream version compare, only when the version string has no vendor marker (.el9, -generic, .amzn, -pve, and similar). Fixed stable releases: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, 7.3. At or above → PATCHED; below → VULNERABLE. A 7.3 release candidate is UNKNOWN because the fix landed at rc7.
  3. Pre-4.4 kernel → NOT_AFFECTED.
  4. Upstream-EOL branch 4.4, 4.9, 4.14, 4.19 or 5.4 → VULNERABLE; no fix will come.
  5. Vendor kernel whose changelog does not mention the CVE → LIKELY_VULNERABLE. Confirm against the vendor advisory; the fix may be pending or the changelog unavailable.
  6. Anything else → UNKNOWN, with the reason string saying which inputs were missing.

Output fields

Human output and JSON carry the same fields. JSON keys are in parentheses.

FieldMeaning
Running kernel (kernel)uname -r or the override.
Kernel package (package, package_version)Installed package for the running kernel, when found.
Changelog has CVE (changelog_mentions_cve)yes, no, unavailable, or not_checked.
Upstream version (upstream_version_verdict)Result of step 2 above, including VENDOR_KERNEL.
net.mptcp.enabled (mptcp_enabled)1 raises exposure; the reported lab exploit targeted MPTCP listeners.
tcp_migrate_req (tcp_migrate_req)1 enables the request-migration variant of the bug. n/a on kernels before 5.14, which have neither the sysctl nor the variant.
IP-options drop rule (ip_options_drop_rule)nftables, iptables, iptables-legacy-location, or no. An nftables table without the drop rule, for example after a flush, reports no.
dropped so far (drop_counter)Packets the rule has dropped. Use it to correlate with remote-probe.py --repeat N.
Interim mitigation (mitigation)none, partial, full, with +mptcp_off when MPTCP is disabled.
Mitigation coverage (mitigation_coverage)complete, or incomplete naming datapaths that bypass host netfilter.
NetLabel/CIPSO (netlabel_cipso)no, or where a CIPSO configuration was found.
Firewall managers (firewall_managers)Active firewalld, ufw, nftables.service, kube-proxy, docker. Informational.
IPv4 TCP / MPTCP listenersCounts from ss. n/a when ss rejects the option, as the Ubuntu 18.04 ss does for MPTCP.
Exposure (exposure)One-line summary of the factors above.
verdict / reasonFinal patch-state verdict and why.

iptables-legacy-location means a rule from an earlier version of this script sits in filter/INPUT. It still protects the host stack but not forwarded container traffic; the next --mitigate moves it.

What --mitigate does

These reduce exposure until the kernel is updated. They are not a fix.

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 →