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-check — Read-only Linux kernel checker for CVE-2026-98432 that detects vulnerable or unpatched kernels, flags reboot-required states, and offers optional patching, sysctl mitigation, and forensics. | Kitploit
Tools/GitHubGitHub/xxhjkl/cve-2026-98432-check
Defensive ToolsVulnerability AnalysisScripting & AutomationConfiguration AuditingForensicsMisconfigurationIncident Response
GitHubxxhjkl/cve-2026-98432-check

cve-2026-98432-check

Read-only Linux kernel checker for CVE-2026-98432 that detects vulnerable or unpatched kernels, flags reboot-required states, and offers optional patching, sysctl mitigation, and forensics.

View Repository
1017 days agoNot yet reviewed
Share

CVE-2026-98432 Check / Remediation Script

A batch check and remediation tool for the race condition → Use-After-Free vulnerability (introduced in Linux 4.4) in the Linux kernel IPv4 TCP handshake path.

  • Vulnerability ID: CVE-2026-98432 (CVSS 3.1 upstream 9.8 / vendors 5.9–8.1)
  • Impact: remotely triggerable without authentication; reliably obtaining root requires the target to have an MPTCP listening socket
  • IPv6: not affected
  • Remediation: upgrade the kernel + reboot

This script is intended for self-checking your own servers and contains no exploit code.

Why this script was written

Manually checking this has three common pitfalls, and the script handles all three:

  1. Distributions backport patches, so comparing only uname -r leads to misjudgment — therefore, for Debian-based systems, it uses dpkg --compare-versions to compare package versions rather than guessing version numbers.
  2. Installing the patch without rebooting is the same as not fixing it — it separately identifies the state where "the fixed kernel is on disk, but the running one is not it" and outputs REBOOT_REQUIRED.
  3. net.mptcp.enabled=1 is the kernel default and does not mean there is an MPTCP listener — the real criterion is whether there is a listening line with netid == mptcp in ss -Mltnp. Moreover, on older kernels ss -M produces false positives, so the script splits results into two tiers: confirmed / suspected.

Quick start

# 只体检,不改任何东西(推荐先跑这个)
curl -fsSL https://raw.githubusercontent.com/xxhjkl/cve-2026-98432-check/main/cve-2026-98432-check.sh -o /tmp/cve-check.sh
less /tmp/cve-check.sh          # 建议先看一眼再执行
sudo bash /tmp/cve-check.sh

For production environments, it is recommended to pin the commit SHA or tag to prevent upstream changes from silently affecting the entire batch of machines:

curl -fsSL https://raw.githubusercontent.com/xxhjkl/cve-2026-98432-check/v2.0/cve-2026-98432-check.sh -o /tmp/cve-check.sh

Parameters

ParameterPurpose
No parametersRead-only health check, outputs a report
--jsonAdditionally outputs one line of JSON for batch aggregation
-q / --quietOutputs only the conclusion line
--fixInstalls/upgrades the kernel package (no reboot)
--mitigateApplies temporary sysctl mitigation when no patch is available
--mitigate --nftAdditionally uses nftables to drop IPv4 TCP packets with IP options
--no-refreshDoes not refresh the apt index (strict read-only scenarios; conclusions may be outdated)
--forensicsAppends a read-only intrusion investigation (takes a dozen seconds)
--since YYYY-MM-DDStart of the investigation time window, defaults to 2026-10-15 (vulnerability disclosure date)
--rebootReboots after installation (prints a countdown first, can be cancelled with Ctrl-C)
-h / --helpUsage

Read-only by default. Without --fix / --mitigate / --reboot, the script will not modify any system state.

Output Conclusions and Exit Codes

statusMeaningExit code
FIXEDRunning kernel already contains the fix0
NOT_AFFECTEDKernel is earlier than 4.4, or the vendor states it is not affected (e.g., RHEL 7)0
REBOOT_REQUIREDFixed version is installed, only a reboot is needed10
PATCH_AVAILABLEA patch exists but is not installed11
NO_FIX_YETAffected and the vendor has no patch yet, temporary mitigation required12
CONTAINERInside a container, the kernel is provided by the host, contact the service provider13
UNKNOWNCannot be determined from the version alone, check the vendor advisory14
EOLThe system is EOL, no official patch will be available15
CUSTOM_KERNELRunning a third-party kernel (XanMod / Liquorix / self-compiled), patches must come from its own source16

Intrusion Investigation (--forensics)

When the report determines the system is affected, adding --forensics appends a read-only investigation. It does not modify any files or clean anything up—forensics comes before remediation.

sudo bash cve-2026-98432-check.sh --forensics
sudo bash cve-2026-98432-check.sh --forensics --since 2026-10-01   # 自定义时间窗

Checks fall into two tiers:

High risk (basically confirms compromise if seen)

CheckCriterion
UID=0 accountsAny UID=0 other than root
/etc/ld.so.preloadNon-empty → userland rootkit injection
Process executablesRunning from /tmp, /dev/shm, or (deleted)

Attention (requires manual review, mostly normal operations)

CheckCriterion
SSH public keysauthorized_keys exists; list count, mtime, command=/from= restrictions
Persistencecron modified within the time window / newly added systemd units / unexpectedly present rc.local
Auth files/etc/passwd, /etc/shadow, /etc/sudoers, sshd_config modified within the time window
Outbound connectionsEstablished connections whose peer is not internal/local
Login recordsSuccessful SSH logins whose source is not internal/local
Binary changesFiles changed within the time window under /usr/local/{bin,sbin}, /root

Output a single summarizable result line at the end:

FORENSICS|serv|high=0|warn=2|since=2026-10-15

Limitations: This is probabilistic detection; passing does not mean absolutely clean. When high is not 0, memory and disk forensics should be performed rather than direct cleanup.

Batch Execution

# 分发
for h in host1 host2 host3; do
  scp -q cve-2026-98432-check.sh "$h:/root/"
done

# 体检并汇总
: > /tmp/cve-report.json
for h in host1 host2 host3; do
  ssh "$h" 'bash /root/cve-2026-98432-check.sh -q --json' >> /tmp/cve-report.json 2>&1
done

grep -oE '"status":"[A-Z_]+"' /tmp/cve-report.json | sort | uniq -c

Covered distributions

DistributionDetermination method
Debian 12 / 13Upstream version number + dpkg --compare-versions, can be determined precisely
Debian ≤ 11Determined as EOL
Ubuntu 16.04–20.04Determined as EOL (vendor explicitly does not provide fixes)
Ubuntu 22.04+Per vendor status table (no fixed kernel as of the baseline date)
RHEL / CentOS / Rocky / Alma / Oracle 7Not affected
RHEL 8/9/10, OpenShiftPer vendor status table (fix postponed as of the baseline date)
Amazon Linux 2023Indicates the fixed package version

Notes

  • The version table baseline date is 2026-11-02. After the vendor releases new patches, the script will be conservative (still reporting NO_FIX_YET). To update: modify the FIXED_PATCH associative array at the top of the file, as well as the version numbers in debian_fixed_pkg().
  • The script never reboots automatically (unless --reboot is explicitly specified). Kernel patches do not take effect without a reboot, which is the most commonly overlooked step in actual remediation.
  • Running it inside a container is meaningless: uname -r shows the host kernel, and neither internal upgrades nor reboots will have any effect.
  • The nftables rules added by --mitigate --nft are lost after a reboot; if needed, write them to /etc/nftables.conf. Do not add this rule on networks that use CIPSO / NetLabel tagging.
  • Temporary mitigation only reduces the attack surface and does not change the vulnerable code in the kernel; once a patch is available, you must still upgrade and reboot.

Changelog

v2.0 (2026-11-02)

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.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    548
  • 3

    redforge

    cybersecurity91/redforge

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

    366
  • 4

    ARTEX

    baarai/artex

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

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

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

    287

Explore all tools

Browse our collection of tools

View all tools →