
Guide and read-only check script for CVE-2026-98432, a Linux IPv4 TCP use-after-free: detect kernel patch status, apply an iptables stopgap, and verify after the fix.
Attackable over the network, with no login and no user action. The bug is in the kernel code that handles every incoming IPv4 TCP connection.
This guide shows how to check a server, protect it until a patched kernel is available, and clean up afterwards. The commands below were used on Ubuntu 22.04 and 24.04 servers.
Status in this document is as of 2026-10-30. Patch status changes quickly, so always check your distribution's own security tracker.
e3f33b0a1d89In plain words: a connection request (SYN) can carry IPv4 options, rarely used extras in the packet header such as Record Route or Timestamp. When one arrives, the kernel keeps a copy of those options. If the attacker resends the SYN at just the right moment, one CPU can free that copy while another is still using it to build the reply. That is a use-after-free in ip_options_build(), and it can crash the server or corrupt kernel memory.
A second trigger exists when the server migrates pending connection requests between sockets (net.ipv4.tcp_migrate_req=1, or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program). That setting is off by default.
| Ubuntu priority | High |
| CVSS, kernel CNA | 9.8 Critical: network, no authentication, no user interaction |
| CVSS, Red Hat | 8.1, because Red Hat considers the race harder to hit |
| Affected | Kernels since 4.4 |
| IPv6 | Not affected by the main issue |
| Exploitation | None reported in the wild, and not in the CISA KEV catalog. A remote root exploit against servers with a multipath TCP (MPTCP) listener has been reported but not published. |
Who is exposed: any server with a TCP port reachable over IPv4, whether SSH, HTTP, HTTPS or anything else.
| Distribution | Status | Fixed in |
|---|---|---|
| Upstream kernel | ✅ Fixed | 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, 7.3 |
| Debian 12 / 13 | ✅ Fixed | 6.1.190-1 (or linux-6.12 6.12.113-1~deb12u1) / 6.12.113-1 |
| Ubuntu 26.10 / 26.04 / 24.04 / 22.04 | ❌ Fix in progress, not released | Planned: 7.3.0-10.10 / 7.0.0-43.43 / 6.8.0-149.149 / 5.15.0-203.213 |
| Ubuntu 20.04 / 18.04 / 16.04 | ❌ Vulnerable | Only through Ubuntu Pro (ESM), if at all |
| RHEL 8 / 9 / 10 | ❌ Reported as "fix deferred" | None |
| Oracle Linux (UEK) | ✅ Fixed | ELSA-2026-500397 / 500398 / 500399 |
| Amazon Linux 2023 | ⚠️ Partly fixed | kernel6.18 and kernel6.12 fixed; default kernel and AL2 pending |
| SUSE | ⚠️ Partly fixed | openSUSE Leap 16.0 fixed; SLES in progress |
Ubuntu cloud kernels (-aws, -azure, -gcp, -oracle) have their own version numbers. Distribution kernels backport fixes, so don't compare a distro version like 5.15.0-xxx with the upstream numbers.
This only reads and reports. It doesn't install, change or restart anything. Paste it into a terminal on the server:
sudo bash -s <<'EOF'
CVE=CVE-2026-98432; FIX="free inet_opt and ireq_opt"; KR=$(uname -r)
. /etc/os-release
echo "== $PRETTY_NAME | running kernel: $KR"; echo " build: $(uname -v)"
echo "== Installed kernels (if one is newer than the running kernel, you need a reboot)"
ls -1v /boot/vmlinuz-* 2>/dev/null | sed 's|/boot/vmlinuz-| |'
[ -f /var/run/reboot-required ] && echo " !! reboot required"
echo "== Is the fix in the RUNNING kernel's changelog?"
if command -v dpkg >/dev/null; then
dpkg-query -W -f=' package version: ${Version}\n' "linux-image-$KR" 2>/dev/null
zgrep -Eqs "$CVE|$FIX" /usr/share/doc/linux-*"$KR"*/changelog.Debian.gz \
&& echo " PATCHED" || echo " NOT FOUND -> likely VULNERABLE"
command -v pro >/dev/null && pro fix "$CVE" --dry-run </dev/null
elif command -v rpm >/dev/null; then
PKG=$(rpm -qf "/lib/modules/$KR/vmlinuz" "/usr/lib/modules/$KR/vmlinuz" "/boot/vmlinuz-$KR" 2>/dev/null | grep -v 'not owned' | head -1)
echo " package: ${PKG:-unknown}"
rpm -q --changelog "$PKG" 2>/dev/null | grep -Eq "$CVE|$FIX" \
&& echo " PATCHED" || echo " NOT FOUND -> likely VULNERABLE"
if command -v zypper >/dev/null; then zypper -n -q lp -a --cve="$CVE" </dev/null
elif command -v dnf >/dev/null; then dnf -q updateinfo list --all --cve="$CVE" </dev/null
elif command -v yum >/dev/null; then yum -q updateinfo list --cve="$CVE" </dev/null; fi
fi
echo "== Exposure"
sysctl net.mptcp.enabled net.ipv4.tcp_migrate_req 2>/dev/null | sed 's/^/ /'
M=$(ss -lnMH 2>/dev/null); echo " MPTCP listeners (reported root-exploit path): ${M:-none}"
echo " TCP listeners not on loopback (attack surface):"
ss -ltnH | awk '$4 !~ /^(127\.|\[::1\])/ {print " "$4}' | sort -u
EOF
Paste it whole: the final EOF must be on its own line with no leading spaces.
Reading the output:
| You see | Meaning | Next |
|---|---|---|
PATCHED | The running kernel already has the fix | You're done |
NOT FOUND -> likely VULNERABLE | No fix in the running kernel | Step 2 |
!! reboot required, or a newer kernel than the running one is listed | A newer kernel is installed but not running yet | Step 3 |
A fix is coming soon (Ubuntu) | Ubuntu hasn't shipped the fix yet | Step 2 now, Step 5 later |
MPTCP listeners: none | The reported root-exploit path doesn't apply right now | — |
A database or cache port such as *:3306, 0.0.0.0:6379 or 0.0.0.0:11211 | It listens on all interfaces | Make sure the firewall blocks it (see the end of Step 4) |
The rule below drops IPv4 TCP packets that carry IP options, which is what an attacker needs to trigger the bug. Normal clients (browsers, SSH, phones, APIs, load balancers) never send IP options, so real traffic isn't affected.
First check which firewall tool the server uses:
systemctl is-active ufw nftables firewalld
If nftables or firewalld is active, reloading that firewall can wipe this rule. Use the nftables variant at the end of this step, or adapt it to your setup.
Install the stopgap. It's a small systemd unit, so the rule comes back after every reboot:
sudo tee /etc/systemd/system/cve-2026-98432.service >/dev/null <<'EOF'
[Unit]
Description=Stopgap for CVE-2026-98432: drop IPv4 TCP packets carrying IP options
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/iptables -t raw -I PREROUTING -p tcp -m u32 --u32 "0>>24&0xF=6:15" -m comment --comment CVE-2026-98432 -j DROP
ExecStop=/usr/sbin/iptables -t raw -D PREROUTING -p tcp -m u32 --u32 "0>>24&0xF=6:15" -m comment --comment CVE-2026-98432 -j DROP
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl daemon-reload && sudo systemctl enable --now cve-2026-98432
sudo iptables -t raw -L PREROUTING -v -n
The last command should list a DROP rule with the comment CVE-2026-98432. The pkts column counts packets it blocked; it should stay at 0 or close to it.
The u32 test 0>>24&0xF=6:15 reads the IPv4 header-length field. A normal header is 5 × 4 = 20 bytes. Anything longer means options are attached, and that packet is dropped. The rule sits in the raw table, which ufw doesn't manage, so your existing firewall rules are untouched.
Check SSH before going further: keep your current session open and log in from a second terminal. Then load your website.
To undo instantly:
sudo systemctl stop cve-2026-98432