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 — CVE-2026-98432 firewall mitigation for unpatched Linux OS. | Kitploit
Tools/GitHubGitHub/carlosbustillordguez/cve-2026-98432-mitigation
Defensive ToolsVulnerability AnalysisScripting & AutomationConfiguration AuditingNetwork SecurityMisconfigurationIncident Response
GitHub
Share
carlosbustillordguez/cve-2026-98432-mitigation

cve-2026-98432-mitigation

CVE-2026-98432 firewall mitigation for unpatched Linux OS.

View Repository
13 days agoNot yet reviewed

CVE-2026-98432 firewall mitigation

CVE-2026-98432-mitigation.sh applies (or removes) a host firewall rule that drops incoming IPv4 TCP packets carrying IPv4 options.

CVE-2026-98432 is a use-after-free flaw in the Linux kernel code that sets up incoming IPv4 TCP connections. A remote attacker can trigger it by sending TCP connection requests that carry IPv4 options to any listening IPv4 TCP port. No credentials or user interaction are needed. The Linux kernel CVE team rates this issue Critical, with a CVSS v3.1 score of 9.8. Operating system vendors rate it between Important and Critical.

Table of Contents:

  • CVE-2026-98432 firewall mitigation
    • Requirements
    • Usage
    • Approach
      • Apply (default)
      • Patch detection
      • Disable (--disable)
      • The rules
    • Examples
      • Check the patch status only
      • Kernel already patched
      • Amazon Linux, kernel updated with --releasever but instance still pinned
      • Amazon Linux, kernel not patched
      • Apply with nft
      • Apply with iptables (nft not installed)
      • Kernel older than 4.4
      • Disable
      • Disable when nothing is loaded
      • Manual checks
    • Notes

Requirements

  • Linux host
  • nft (nftables) or iptables (with the u32 match module)
  • Root, or a user with sudo (the script uses sudo only when not run as root)

Usage

chmod +x CVE-2026-98432-mitigation.sh

./CVE-2026-98432-mitigation.sh            # apply the mitigation unless the running kernel is confirmed patched (ignored on Amazon Linux)
./CVE-2026-98432-mitigation.sh --check    # only report the kernel patch status, change nothing
./CVE-2026-98432-mitigation.sh --force    # apply the mitigation even if the kernel looks patched (ignored on Amazon Linux)
./CVE-2026-98432-mitigation.sh --disable  # remove the mitigation (skipped on Amazon Linux)
./CVE-2026-98432-mitigation.sh --help     # show usage

--check, --force and --disable are mutually exclusive. Any unknown option prints the usage text and exits with status 1.

Approach

Apply (default)

  1. Kernel check. Reads uname -r and takes the major.minor part. The script continues only if that is 4.4 or later (compared with sort -V), matching the AWS bulletin's "4.4 and later". Kernels older than 4.4 exit with status 0 and no changes.
  2. Patch status check. Distros backport the fix, so the version number alone cannot tell whether a kernel is patched. The script looks for the CVE in the distro metadata of the package that owns the running kernel (a patched kernel that is installed but not booted does not count). See Patch detection.
    • Amazon Linux: the mitigation is never applied, not even with --force, because patched kernels are available and updating the kernel is the right solution. If the kernel is not confirmed patched, the script prints the AWS bulletin link and exits 0.
    • Other distributions, patched: the script prints that no mitigation is needed and exits 0 (unless --force is given).
    • Other distributions, not-patched or unknown: the mitigation is applied. The check is fail-closed, so the firewall rule is added unless the kernel is positively confirmed patched. This covers distros that have not released a fix yet.
  3. Tool selection. Uses command -v to detect what is installed. nft is preferred; iptables is used only if nft is missing. Only one tool is used, so the rule is never applied twice.
  4. nft path
    • Writes the ruleset to /etc/cve-2026-98432.nft.
    • Deletes a previously loaded inet cve_2026_98432 table, if any (so re-runs are idempotent).
    • Validates with nft -c -f, then loads with nft -f.
    • Adds include "/etc/cve-2026-98432.nft" to /etc/nftables.conf if not already there.
    • Validates /etc/nftables.conf and runs systemctl enable nftables.service so the rule survives a reboot.
  5. iptables path
    • Checks with iptables -C whether the rule exists; if not, inserts it at position 1 of INPUT.
    • Lists INPUT with -n -v --line-numbers.
    • The rule is defined once, in the IPT_ARGS array, and reused for check, insert, delete and verification.
  6. Confirmation. Checks that the rule is present and prints an ACTION: line saying which tool added it (rule ADDED using nft or rule ADDED using iptables). If the rule is not found it prints ACTION: rule was NOT added. to stderr. Exit status is 0 on success, 1 otherwise.

Patch detection

The distribution is read from ID and ID_LIKE in /etc/os-release.

DistributionMethod
Amazon Linux 2023, RHEL family (amzn, rhel, fedora, centos) with dnfdnf -q updateinfo list --installed --cves CVE-2026-98432. The kernel package line must match the running kernel exactly. On Amazon Linux, if nothing matches, the query is repeated with --releasever=latest.
Same family without dnf (for example Amazon Linux 2)Search rpm -q --changelog of the package owning /boot/vmlinuz-$(uname -r) for the CVE.
Debian, UbuntuSearch /usr/share/doc/linux-image-$(uname -r)/changelog.Debian.gz (or changelog.gz) for the CVE.
Anything elseStatus unknown, so the mitigation is applied.

With dnf, the command lists installed packages covered by an advisory for the CVE, for example:

ALAS2023-2026-3335 Important/Sec. kernel6.12-1:6.12.113-138.209.amzn2023.x86_64
ALAS2023-2026-3335 Important/Sec. kernel6.12-devel-1:6.12.113-138.209.amzn2023.x86_64

The script keeps only the kernel/kernelX.Y package whose version-release.arch equals uname -r. The -headers, -devel and -tools packages and other installed kernels are ignored. If there is no output apart from the metadata line, the status is not-patched. If dnf itself fails (for example no repository metadata), the status is unknown.

Amazon Linux 2023 and pinned releases. The repository metadata follows the release the instance is pinned to ($releasever). A kernel installed with dnf update --advisory ... --releasever=<newer release> is not linked to its advisory by a plain dnf updateinfo afterwards, because --releasever is not saved and the older metadata does not contain the advisory. On Amazon Linux, when the first query finds no advisory for the running kernel, the script repeats it with --releasever=latest. The flag applies to that single dnf run only; nothing is written to /etc/dnf/vars. If the second query matches, the status is patched and the detail says it was found only with --releasever=latest. The second query needs access to the Amazon Linux repositories; if it fails and the first query found nothing, the status is unknown rather than not-patched.

On Amazon Linux (ID=amzn), any status other than patched (not-patched or unknown) prints an extra line pointing to the AWS bulletin, in both normal and --check runs:

Please update the Kernel version, see https://aws.amazon.com/security/security-bulletins/2026-160-aws/

The line is not printed when the kernel is patched, or on other distributions. On Amazon Linux the script then stops without touching the firewall (see Apply).

Statuses:

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 →