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.
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.
| Script | For |
|---|---|
mptcp-check-rhel.sh | RHEL, CentOS, Rocky, AlmaLinux, Oracle Linux, Fedora |
mptcp-check-debian.sh | Debian, 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.
Fuentes:
It may be outdated: always verify in your distribution's security advisory.
| Distribution | Status |
|---|---|
| RHEL 9 | Fixed kernel 5.14.0-687.64.1.el9_8 (RHSA-2026:93412), published on 11/1 according to RFF |
| Rocky 9 | RFF 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 bookworm | Fixed (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 |
| Ubuntu | The title of the RFF article indicates that the patches are in -proposed |
| RHEL 7 | Not affected |
It depends on the distribution, and that is why the scripts do not assume it: they detect it.
net.mptcp.enabled=0) and must be enabled with a sysctl file. (From memory; confirm it with sysctl net.mptcp.enabled.)1). On an Ubuntu 24.04 where I tested the script it appeared as 1.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.)
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:
| Scenario | When | What it proposes |
|---|---|---|
| A. MPTCP off | Disabled (by default or by configuration) or the kernel does not include it | Does 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 listeners | net.mptcp.enabled=1 but nobody is listening with MPTCP | With --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 listeners | Processes listening with MPTCP or services forced with mptcpize | The 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.
--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.
ip cve_2026_98432 table and saved to /etc/cve-2026-98432-block-ip-options.nft.nftables is stopped or reloaded. Test it first on a non-production host.--remove-nft after installing the fixed kernel.| Code | Meaning |
|---|---|
0 | The kernel in use appears to have the patch, or is not affected by version (earlier than 4.4) |
1 | The kernel appears unpatched (or it could not be determined): there are recommended actions |
2 | Usage error, permissions or unsupported system |
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.
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.