CVE-2026-98432 is a use-after-free bug in the Linux kernel’s IPv4 TCP handshake. Anyone who can send a SYN to a listening port can reach it. Your application never sees a single byte. The bug goes back to Linux 4.4. Check your distribution and kernel flavor in the tables below.
Updates#
- 7 November 2026, 06:19 UTC. Added the exact OpenShift 4.22.22 x86_64 production release and updated older Ubuntu generic kernels to fixes in progress in the distribution table .
- 6 November 2026, 04:43 UTC. Added the exact Ubuntu 26.04 NVIDIA production branch to the distribution table . Generic HWE status remains separate.
- 6 November 2026, 01:57 UTC. Confirmed Ubuntu 24.04 generic 6.8 in production in the distribution table . Generic HWE status remains separate.
- 6 November 2026, 01:42 UTC. Confirmed Ubuntu 26.04 generic 7.0 in production and added two exact NVIDIA branches to the distribution table . Generic HWE status remains separate.
- 6 November 2026, 01:27 UTC. Added the exact Ubuntu 22.04 NVIDIA standard and low-latency production kernels to the distribution table . Generic HWE status remains separate.
- 5 November 2026, 23:57 UTC. Added five more exact Ubuntu cloud and specialist branches to the distribution table . Generic and generic HWE status remains separate.
- 5 November 2026, 23:44 UTC. Confirmed Ubuntu 22.04 generic 5.15 in production and added the exact released cloud and specialist kernels for 24.04, 22.04 and 26.04 to the distribution table . Generic HWE status remains separate.
- 5 November 2026, 21:13 UTC. Confirmed SLES 12 SP5 LTSS and LTSS Extended Security replacement kernels in the distribution table , with exact subscription and architecture scope.
- 5 November 2026, 16:12 UTC. Split SLES 12 SP5 replacement streams in the distribution table : the tracker marks LTSS kernels released, but exact production packages remain unconfirmed.
- 5 November 2026, 13:42 UTC. Added the exact-base Leap 15.6 live patch for kernel 6.4.0-150600.23.138-default, released 4 November.
- 5 November 2026, 08:43 UTC. Added four more exact-base SUSE live patches for SLES 15 SP7 and SLES 12 SP5, released 4 November.
- 4 November 2026, 18:58 UTC. Updated Leap 15.6 in the distribution table : the vendor tracker says released, but the replacement package and production availability remain unconfirmed.
- 4 November 2026, 15:12 UTC. Added five more exact-base SUSE live patches for SLES 15 SP7 and SLES 12 SP5.
- 4 November 2026, 08:57 UTC. Confirmed SLES 15 SP7 default, 64kb and Azure replacement kernels in the distribution table , with exact architecture scope and reboot requirements.
- 4 November 2026, 06:25 UTC. Added the RHEL 8.6 x86_64 fix for selected extended-support products to the distribution table .
- 3 November 2026, 20:28 UTC. Added seven more exact-base SUSE live patches for SLES 15 SP7, SLES 12 SP5 and Leap 15.6. Replacement kernel releases remain unconfirmed.
- 3 November 2026, 17:54 UTC. Added the RHEL 9.2 x86_64 real-time fix for SAP Solutions and Extended Life Cycle products to the distribution table .
- 3 November 2026, 16:39 UTC. Added the RHEL 8.4 x86_64 fix for selected extended-support products to the distribution table .
- 3 November 2026, 14:13 UTC. Corrected the exposure check
: MPTCP is a requirement of the published exploit, not of the bug. Any host accepting IPv4 TCP from an untrusted network is exposed. Added the
tcp_migrate_reqroute and credited the reporter and the patch authors. - 3 November 2026, 14:11 UTC. Confirmed Oracle 9.8 RHCK in production and added selected RHEL 9.2, 9.6 and 10.0 extended-support fixes to the distribution table .
- 3 November 2026, 12:55 UTC. Added seven more exact-base SUSE live patches ; recorded Oracle 9.8 RHCK’s advisory with production availability still unconfirmed in the distribution table .
- 3 November 2026 (UTC). Added production fixes for Ubuntu 26.10 cloud, Raspberry Pi, real-time and RISC-V kernels, with exact versions and architectures in the distribution table .
- 3 November 2026 (UTC). Confirmed Ubuntu 26.10 generic on amd64/arm64 in production and identified the LTS testing builds in the distribution table .
- 3 November 2026 (UTC). Removed repeated release announcements and made the distribution table the main status reference.
- 3 November 2026 (UTC). Recorded selected RHEL 8.8 and 9.4 extended-support fixes, and Ubuntu 20.04 HWE’s progress.
- 2 November 2026 (UTC). Recorded RHEL, AlmaLinux and Oracle RHCK production fixes for the releases and architectures listed below.
- 2 November 2026 (UTC). Expanded the SUSE live-patch table , including selected Leap 15.6 base kernels.
- 2 November 2026 (UTC). Added Go settings and the community XDP filter , with their limitations.
- 1 November 2026 (UTC). Published the upstream and distro status tables and temporary mitigation checks.
Which distributions are still vulnerable#
Remaining unpatched streams checked on 7 November 2026 (UTC), using vendor trackers, release advisories and production repositories. Previously confirmed fixes retain their original verification dates. Green means a fix is available for the listed release, flavor and architecture. Amber is still vulnerable: work is in progress, but no fixed kernel has been released.
- ✔Fixed
- in progressVulnerable, fix being prepared
- no fixVulnerable, no fixed kernel released
- ?Release not confirmed
| Distribution | Status |
|---|---|
| Debian | |
Debian 12 bookwormlinux 6.1.190-1 (DLA-4841-1), linux-6.12 6.12.113-1~deb12u1 | ✔ |
| Debian 13 trixie6.12.113-1 (DSA-6568-1) | ✔ |
| Debian forky, sid | ✔ |
| Ubuntu | |
Ubuntu 24.04 generic (including arm64 64k)amd64, arm64, armhf, ppc64el, s390xlinux 6.8.0-149.149; kernel images and arm64 64k image published 5–6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
Ubuntu 22.04 generic (including arm64 64k and armhf lpae)amd64, arm64, armhf, ppc64el, s390xlinux 5.15.0-203.213; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.04 generic (including arm64 64k)amd64, amd64v3, arm64, armhf, ppc64el, s390xlinux 7.0.0-43.43; kernel images and arm64 64k image published 5–6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
| Ubuntu generic HWE: 24.04 (7.0), 22.04 (6.8), 20.04 (5.15)Each HWE branch has its own status on the tracker | in progress |
Ubuntu 20.04, 18.04, 16.04Generic linux kernel; Ubuntu Pro required. The vendor tracker lists fixes in progress; no fixed production kernel verified. | in progress |
Ubuntu 26.10 genericamd64, amd64v3, arm64, armhf, ppc64el, s390xlinux 7.3.0-10.10; Canonical's fix announcement and production package. Published in -updates on 28 October and -security on 2 November (amd64 record, arm64 record, other binary records). | ✔ |
| Remaining Ubuntu HWE, cloud and specialist branchesNo production fix confirmed for the remaining branches; progress varies by flavor. Match the exact source package and release on the tracker and the production records below. | no fix |
Ubuntu 24.04 AWS (including arm64 64k)amd64, arm64linux-aws 6.8.0-1069.74; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 GCP (including arm64 64k)amd64, arm64linux-gcp 6.8.0-1073.81; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 GCP 7.0 (including arm64 64k)amd64, arm64linux-gcp-7.0 7.0.0-1017.19~24.04.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 GKE on-premisesamd64linux-gkeop 6.8.0-1053.57; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 IBMamd64linux-ibm 6.8.0-1069.70; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 Raspberry Piarm64linux-raspi 6.8.0-1068.72; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 Low-latency 6.8 (including arm64 64k)amd64, arm64linux-lowlatency 6.8.0-149.149.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 24.04 NVIDIA 7.0 (including arm64 64k)amd64, arm64linux-nvidia-7.0 7.0.0-1025.26~24.04.1; kernel images and arm64 64k image published 6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
Ubuntu 22.04 AWS (including arm64 64k)amd64, arm64linux-aws 5.15.0-1120.127; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 AWS 6.8 (including arm64 64k)amd64, arm64linux-aws-6.8 6.8.0-1069.74~22.04.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 GCPamd64, arm64linux-gcp 5.15.0-1121.131; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 GCP 6.8 (including arm64 64k)amd64, arm64linux-gcp-6.8 6.8.0-1073.81~22.04.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 GKEamd64, arm64linux-gke 5.15.0-1116.122; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 GKE on-premisesamd64linux-gkeop 5.15.0-1103.111; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 IBM 6.8amd64linux-ibm-6.8 6.8.0-1069.70~22.04.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 KVMamd64linux-kvm 5.15.0-1112.117; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 Low-latency 5.15 (including arm64 64k)amd64, arm64linux-lowlatency 5.15.0-198.208; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 Low-latency HWE 6.8 (including arm64 64k)amd64, arm64linux-lowlatency-hwe-6.8 6.8.0-149.149.1~22.04.1; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 22.04 NVIDIA (standard and low-latency)amd64linux-nvidia 5.15.0-1115.116; NVIDIA kernel image and low-latency kernel image published 6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
Ubuntu 26.04 AWS (including arm64 64k)amd64, amd64v3, arm64linux-aws 7.0.0-1017.18; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.04 GCP (including arm64 64k)amd64, amd64v3, arm64linux-gcp 7.0.0-1017.19; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.04 GKE (including arm64 64k)amd64, amd64v3, arm64linux-gke 7.0.0-1010.11; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.04 IBMamd64, amd64v3linux-ibm 7.0.0-1018.18; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.04 NVIDIA (including arm64 64k)amd64, amd64v3, arm64linux-nvidia 7.0.0-1025.26; kernel images and arm64 64k image published 6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
Ubuntu 26.04 NVIDIA BOS (including arm64 64k)amd64, amd64v3, arm64linux-nvidia-bos 7.0.0-2024.25; kernel images and arm64 64k image published 6 November in -updates; IPv4 RCU fix in changelog. Verified 6 November (UTC). | ✔ |
Ubuntu 26.04 OEM 7.0amd64, amd64v3linux-oem-7.0 7.0.0-1018.18; kernel images published 5 November in -updates; IPv4 RCU fix in changelog. Verified 5 November (UTC). | ✔ |
Ubuntu 26.10 AWS (including arm64 64k)amd64, amd64v3, arm64linux-aws 7.3.0-1004.4; kernel images published 2 November in -security; fix in changelog | ✔ |
Ubuntu 26.10 Azure (including arm64 64k)amd64, amd64v3, arm64linux-azure 7.3.0-1004.4; kernel images published 29 October in -updates; fix in changelog | ✔ |
Ubuntu 26.10 GCP (including arm64 64k)amd64, amd64v3, arm64linux-gcp 7.3.0-1004.4; kernel images published 2 November in -security; fix in changelog | ✔ |
Ubuntu 26.10 Oracle cloud (including arm64 64k)amd64, amd64v3, arm64linux-oracle 7.3.0-1004.4; kernel images published 2 November in -security; fix in changelog | ✔ |
Ubuntu 26.10 Raspberry Pi (standard and real-time)arm64linux-raspi 7.3.0-1004.4; kernel images published 2 November in -security; fix in changelog | ✔ |
Ubuntu 26.10 Azure FDEamd64, amd64v3linux-azure-fde 7.3.0-1004.5; kernel images published 29 October in -updates; fix in changelog | ✔ |
Ubuntu 26.10 Real-time (including arm64 64k)amd64, amd64v3, arm64linux-realtime 7.3.0-10.10.1; kernel images published 2 November in -security; fix in changelog | ✔ |
Ubuntu 26.10 RISC-V genericriscv64linux-riscv 7.3.0-10.10.1; kernel images published 2 November in -security; fix in changelog | ✔ |
| RHEL and clones | |
RHEL 8.4, selected extended-support streamsx86_64kernel 4.18.0-305.218.1.el8_4, released 3 November; Advanced Mission Critical Update Support and Extended Update Support Long-Life Add-On products listed in RHSA-2026:94623 | ✔ |
RHEL 8.6, selected extended-support streamsx86_64kernel 4.18.0-372.227.1.el8_6, released 4 November; Advanced Mission Critical Update Support and Extended Update Support Long-Life Add-On products listed in RHSA-2026:94996 | ✔ |
RHEL 8.8, selected extended-support streamsx86_64; SAP Solutions also ppc64lekernel 4.18.0-477.178.1.el8_8, released 3 November; Update Services for SAP Solutions, TUS and Extended Life Cycle Long Life products listed in RHSA-2026:94303 | ✔ |
RHEL 8.10kernel 4.18.0-553.182.1.el8_10, released 1 November (RHSA-2026:93414) | ✔ |
RHEL 8.10 real-timekernel-rt 4.18.0-553.182.1.rt7.523.el8_10, released 1 November (RHSA-2026:93415) | ✔ |
RHEL 9.2, selected extended-support streamsaarch64, ppc64le, s390x, x86_64kernel 5.14.0-284.202.1.el9_2, released 3 November; AUS, Update Services for SAP Solutions, four-year update and Extended Life Cycle products listed in RHSA-2026:94477 | ✔ |
RHEL 9.2 real-time, selected extended-support streamsx86_64kernel-rt 5.14.0-284.202.1.rt14.487.el9_2, released 3 November; Update Services for SAP Solutions and Extended Life Cycle products listed in RHSA-2026:94558 | ✔ |
RHEL 9.4, selected extended-support streamsaarch64, ppc64le, s390x, x86_64kernel 5.14.0-427.161.1.el9_4, released 2 November; AUS, Update Services for SAP Solutions, four-year update and Extended Life Cycle products listed in RHSA-2026:94109 | ✔ |
RHEL 9.6, selected extended-support streamsaarch64, ppc64le, s390x, x86_64kernel 5.14.0-570.154.1.el9_6, released 3 November; EUS, AUS, Update Services for SAP Solutions, four-year update and Extended Life Cycle products listed in RHSA-2026:94438 | ✔ |
RHEL 9.8kernel 5.14.0-687.64.1.el9_8, released 1 November (RHSA-2026:93412) | ✔ |
RHEL 10.0, extended-support streamsaarch64, ppc64le, s390x, x86_64kernel 6.12.0-55.117.1.el10_0, released 3 November; EUS and four-year update products listed in RHSA-2026:94508 | ✔ |
RHEL 10.2kernel 6.12.0-211.72.1.el10_2, released 1 November (RHSA-2026:93413) | ✔ |
NVIDIA on RHEL 10aarch64kernel and kernel-64k 6.12.0-265.31.el10nv, released 2 November (RHSA-2026:93775) | ✔ |
| OpenShift Container Platform 4.22.22x86_64RHCOS kernel fix included in the 4.22.22 platform update, released 6 November. The production release payload matches the advisory digest and is listed in stable-4.22. Upgrade through the supported OpenShift update path; this does not establish fixes for other OpenShift streams. Verified 7 November (UTC). | ✔ |
| Other RHEL kernel streams and remaining OpenShift releasesNo released fix confirmed beyond the exact streams above; check the matching product advisory | not confirmed |
AlmaLinux 8.10kernel 4.18.0-553.182.1.el8_10, verified in production on 2 November (ALSA-2026:93414) | ✔ |
AlmaLinux 9.8x86_64kernel 5.14.0-687.64.1.el9_8, verified in production BaseOS on 2 November; package changelog names this CVE | ✔ |
AlmaLinux 10.2x86_64kernel 6.12.0-211.72.1.el10_2, verified in production BaseOS on 2 November; package changelog names this CVE | ✔ |
| Oracle Linux 7 to 10UEKFixed on 16 October | ✔ |
Oracle Linux 10.2RHCK, x86_64kernel 6.12.0-211.72.1.el10_2, released 2 November (ELSA-2026-93413) | ✔ |
Oracle Linux 8.10RHCK, x86_64kernel 4.18.0-553.182.1.el8_10, released 2 November (ELSA-2026-93414) | ✔ |
Oracle Linux 9.8RHCK, x86_64kernel 5.14.0-687.64.1.el9_8, released 2 November (ELSA-2026-93412); verified in production BaseOS on 3 November (UTC). | ✔ |
| Oracle Linux 7 and remaining 9 RHCK streamsRed Hat compatible kernel, no released fix confirmed | no fix |
| SUSE | |
SLES 16.0, openSUSE Leap 16.0kernel-default 6.12.0-160000.40.1 | ✔ |
| SLES 15 SP4, SP5, SP6 (LTSS) | ✔ |
SLES 15 SP7 default replacement kernelaarch64, ppc64le, s390x, x86_64kernel-default 6.4.0-150700.53.90.1; Basesystem Module, released 3 November in SUSE-SU-2026:5091-1; production availability verified 4 November (UTC). Install with zypper patch, reboot and verify the running kernel. | ✔ |
SLES 15 SP7 64kb replacement kernelaarch64kernel-64kb 6.4.0-150700.53.90.1; Basesystem Module (SUSE-SU-2026:5091-1), released 3 November; verified 4 November (UTC). Reboot required. | ✔ |
SLES 15 SP7 Azure replacement kernelaarch64, x86_64kernel-azure 6.4.0-150700.53.90.1; Public Cloud Module (SUSE-SU-2026:5091-1), released 3 November; verified 4 November (UTC). Reboot required. | ✔ |
| Other SLES 15 SP7 replacement flavors, including real-timeNo released replacement confirmed; match the exact flavor on the vendor tracker. | not confirmed |
| SLES 15 SP7 default, selected base kernelsppc64le, s390x, x86_64 live patches available; exact packages below | live patches |
| SLES 15 SP7 real-time, selected base kernelsx86_64 live patches available; exact packages below | live patches |
SLES 12 SP5 LTSS replacement kernelaarch64, ppc64le, s390x, x86_64kernel-default 4.12.14-122.339.1, released 5 November in SUSE-SU-2026:5121-1; production availability verified 5 November (UTC). LTSS subscription required. Install with zypper patch, reboot and verify the running kernel. | ✔ |
SLES 12 SP5 LTSS Extended Security replacement kernelx86_64kernel-default 4.12.14-122.339.1, released 5 November (SUSE-SU-2026:5121-1); production availability verified 5 November (UTC). LTSS Extended Security subscription required. Reboot required. | ✔ |
SLES 12 SP5, other replacement streamsServer and High Performance Computing kernel-source remain affected on the vendor tracker; LTSS status above does not establish a fix for these products. | no fix |
| SLES 12 SP5, selected base kernelsLive patches available; exact packages below | live patches |
openSUSE Leap 15.6 replacement kernelVendor tracker: kernel-default and kernel-source marked released. Exact fixed replacement version and production availability remain unconfirmed, checked 4 November (UTC). | not confirmed |
| openSUSE Leap 15.6, selected base kernelsLive patches available; exact packages below | live patches |
| Amazon | |
| Amazon Linux 2 and 2023Every kernel, 24 to 30 October | ✔ |
Match the advisory’s product and architecture list to your installation, especially for RHEL extended-support subscriptions. An RHEL fix doesn’t establish that an OpenShift or RHEL CoreOS update has shipped. A fixed package being available doesn’t mean your running kernel is patched.
Ubuntu’s CVE tracker can lag production publication. The linked kernel-image records and changelogs establish the fixed releases above, including the IPv4 RCU fix named in the CVE. For remaining Ubuntu branches, testing builds in -proposed are a separate option for users who can run their own kernel acceptance tests
. They haven’t completed Canonical’s qualification testing. Follow Ubuntu’s selective testing instructions
if you choose that route; don’t enable broad upgrades from -proposed. Reboot into the fixed kernel and verify uname -r afterwards. Generic, HWE, low-latency and cloud kernels have separate statuses.
SUSE live patches#
These packages apply only to the exact base kernel, flavor and architecture listed. They don’t establish that a replacement kernel is available. Match the advisory to your running kernel and check that live patching is supported and active; installing the package alone doesn’t establish that the patch is active.
| Release | Fixed live-patch package | SUSE-SU-2026 |
|---|---|---|
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_75-rt-3-150700.2.1 | 4960-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_28-rt-15-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_31-rt-14-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_34-rt-12-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_37-rt-12-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_44-rt-10-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_51-rt-9-150700.2.1 | 4964-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_62-rt-7-150700.2.1 | 4966-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_67-rt-5-150700.2.1 | 4966-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_19-rt-17-150700.2.1 | 4968-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_25-rt-15-150700.2.1 | 4968-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_22-rt-16-150700.2.1 | 4969-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_78-rt-2-150700.2.1 | 4971-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_81-rt-2-150700.2.1 | 4971-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_283-default-16-2.1 | 4972-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_275-default-18-2.1 | 4979-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_280-default-16-2.1 | 4980-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_290-default-16-2.1 | 4980-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_40-rt-11-150700.2.1 | 4984-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_73-default-17-150600.2.1 | 4990-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_78-default-15-150600.2.1 | 4990-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_81-default-15-150600.2.1 | 4990-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_100-default-11-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_103-default-10-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_109-default-9-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_112-default-9-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_118-default-8-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_84-default-15-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_87-default-14-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_92-default-12-150600.2.1 | 5002-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_95-default-12-150600.2.1 | 5002-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_293-default-15-2.1 | 5006-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_296-default-12-2.1 | 5006-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_299-default-12-2.1 | 5006-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_302-default-11-2.1 | 5006-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_115-default-8-150600.2.1 | 5016-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_125-default-6-150600.2.1 | 5053-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_130-default-5-150600.2.1 | 5055-1 |
| openSUSE Leap 15.6ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150600_23_138-default-2-150600.2.1 | 5107-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_31-default-14-150700.2.1 | 5016-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_34-default-12-150700.2.1 | 5016-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_37-default-12-150700.2.1 | 5016-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_40-default-11-150700.2.1 | 5016-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_45-default-10-150700.2.1 | 5016-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_307-default-9-2.1 | 5019-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_72-rt-5-150700.2.1 | 5020-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_54-rt-8-150700.2.1 | 5024-1 |
| SLES 15 SP7 RTx86_64 | kernel-livepatch-6_4_0-150700_7_59-rt-8-150700.2.1 | 5024-1 |
| SLES 15 SP7ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_19-default-17-150700.2.1 | 5030-1 |
| SLES 15 SP7ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_22-default-15-150700.2.1 | 5030-1 |
| SLES 15 SP7ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_25-default-15-150700.2.1 | 5030-1 |
| SLES 15 SP7ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_28-default-15-150700.2.1 | 5033-1 |
| SLES 15 SP7ppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_52-default-9-150700.2.1 | 5033-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_55-default-8-150700.2.1 | 5053-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_60-default-8-150700.2.1 | 5053-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_73-default-6-150700.2.1 | 5059-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_78-default-5-150700.2.1 | 5058-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_320-default-6-2.1 | 5034-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_317-default-7-2.1 | 5048-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_310-default-9-2.1 | 5052-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_63-default-7-150700.2.1 | 5081-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_66-default-7-150700.2.1 | 5081-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_81-default-3-150700.2.1 | 5085-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_323-default-5-2.1 | 5086-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_328-default-2-2.1 | 5088-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_84-default-2-150700.2.1 | 5103-1 |
| SLES 15 SP7 defaultppc64le, s390x, x86_64 | kernel-livepatch-6_4_0-150700_53_87-default-2-150700.2.1 | 5103-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_333-default-2-2.1 | 5103-1 |
| SLES 12 SP5ppc64le, s390x, x86_64 | kgraft-patch-4_12_14-122_336-default-2-2.1 | 5103-1 |
Fixed upstream kernels#
If you run a kernel.org stable kernel, these are the first fixed releases:
| Branch | Fixed in | Released |
|---|---|---|
| 7.3 | 7.3 | 18 October |
| 7.2 | 7.2.10 | 11 October |
| 6.18 | 6.18.56 | 11 October |
| 6.12 | 6.12.113 | 15 October |
| 6.6 | 6.6.159 | 15 October |
| 6.1 | 6.1.190 | 15 October |
| 5.15 | 5.15.223 | 15 October |
| 5.10 | 5.10.272 | 15 October |
| 4.4 to 5.4End of life | no fix |
Anything older than those, on that branch, is vulnerable. Distro kernels have their own version numbers and their own backported fixes. For those, check the distro’s own tracker, not uname -r against this table. Xinyang Ge reported the bug. Eric Dumazet wrote the fix. Kuniyuki Iwashima reviewed it.
Am I exposed?#
Two checks. First, compare your kernel with your distro’s tracker:
$ uname -r
7.0.0-42-generic
That Ubuntu 26.04 kernel is vulnerable. Use the distribution table and vendor tracker to check yours.
Second, ask whether anything accepts IPv4 TCP from a network you don’t trust. An attacker reaches the bug with one incoming SYN that carries IPv4 options. Any listening IPv4 TCP port will do. No special protocol, no special setting. If an untrusted network can open an IPv4 TCP connection to your box, treat the box as exposed.
There is a second way to reach the bug, through request socket migration. That needs net.ipv4.tcp_migrate_req=1 or a BPF migration program. It is off by default. The same patch fixes both.
The exploit needs MPTCP. The bug does not#
The researcher who reported this bug works at Anthropic. Their published exploit needs a Multipath TCP (MPTCP) listener on the target. The bug itself does not need MPTCP. AlmaLinux says it plainly. The bug is in the regular IPv4 TCP code. Systems without MPTCP still need the fix. The Go Security Team agrees. It adds that systems with no MPTCP listeners may be vulnerable to similar attacks.
So counting your MPTCP listeners only tells you whether the one published exploit can reach you. It does not tell you whether you are vulnerable. Count them anyway. The number surprised me:
$ sysctl net.mptcp.enabled
net.mptcp.enabled = 1
$ sudo ss -Mlnp | awk 'NR>1{print $6}' | grep -oE '\(\("[^"]+"' | sort | uniq -c
711 (("tailscaled"
1 (("whatsapp-mcp"
712 MPTCP listeners. I never asked for a single one. They’re all Go programs. tailscaled has one listener per tailscale serve
port, on the tailnet IPv4 and IPv6 address. The other one is a small MCP server on 127.0.0.1. Since Go 1.24, Go turns MPTCP on by default for listening sockets, as long as the kernel allows it. A lot of infrastructure is written in Go these days. Run that ss on your own boxes too.
Every one of those listens on Tailscale or localhost. Only devices on my tailnet can reach them. But that box also answers SSH on a public port. So an untrusted network can still open an IPv4 TCP connection to it. By the check that actually matters, it is exposed. The MPTCP count never would have told me that.
Blocking it until your distro catches up#
A replacement kernel needs a reboot to take effect; SUSE also has the live-patch route described above for selected kernels. Until a fix is active, drop every IPv4 TCP packet that carries IP options. Almost no legitimate traffic sets them. This blocks the incoming IP options used by the demonstrated attack. This is the rule AlmaLinux published
. It hooks into prerouting, so it runs before anything else touches the packet:
nft add table ip cve_2026_98432
nft add chain ip cve_2026_98432 pre '{ type filter hook prerouting priority -300; }'
nft add rule ip cve_2026_98432 pre meta l4proto tcp ip hdrlength gt 5 counter drop
ip hdrlength counts the IPv4 header in 4-byte words. A header without options is 5 words (20 bytes). Anything above 5 carries options.
I tested it in a throwaway network namespace. A small Python script opens two connections to a local listener. One is plain. The other sets a Record Route option through IP_OPTIONS.
$ sudo ip netns add cve98432
$ sudo ip -n cve98432 link set lo up
$ sudo ip netns exec cve98432 python3 syn.py
plain SYN: connected
SYN with Record Route: connected
Then the same, with the three nft lines above added inside the namespace:
$ sudo ip netns exec cve98432 python3 syn.py
plain SYN: connected
SYN with Record Route: TimeoutError
$ sudo ip netns exec cve98432 nft list table ip cve_2026_98432
table ip cve_2026_98432 {
chain pre {
type filter hook prerouting priority raw; policy accept;
meta l4proto tcp ip hdrlength > 5 counter packets 3 bytes 300 drop
}
}
Three packets dropped: the SYN and two retransmits. Each is 100 bytes: 20 bytes of IP header, 40 of options, 40 of TCP. The plain connection is untouched.
The rule is in memory only. Save it in /etc/nftables.conf, or it’s gone at the next reboot. (Admittedly, that reboot is also when you’d boot the fixed kernel.) Container traffic that’s bridged on the same host can bypass a prerouting hook on the host. And don’t use it on networks that rely on CIPSO security labels. Those travel as IP options. Red Hat publishes a version
on the input hook. It says the rule “reduces exposure to this vulnerability but cannot fully prevent it”. The same goes for every rule here. It’s a temporary measure, not a fix.
You can also turn MPTCP off if you don’t use it. That takes away what the published exploit needs. It does not remove the bug:
echo 'net.mptcp.enabled = 0' | sudo tee /etc/sysctl.d/99-no-mptcp.conf
sudo sysctl --system
That only affects sockets created afterwards. Restart the services that listen. It’s also set per network namespace, so containers need it too (docker run --sysctl net.mptcp.enabled=0 ...). I’d still add the nft rule. The bug is in the IPv4 handshake. MPTCP is just the one way in that’s been proven to work.
More mitigation options#
The Go Security Team
also documents a per-program option. It calls that option “a fragile mitigation”. The option only helps if every workable exploit for this bug needs MPTCP. Set GODEBUG=multipathtcp=0 in the service’s environment, then restart it. If you’re building the program yourself, godebug multipathtcp=0 in the main module’s go.mod changes the build-time default. An explicit net.ListenConfig.SetMultipathTCP call overrides these defaults. Check the listeners again after restarting. Leaving one exposed MPTCP listener is enough to leave the demonstrated exploit’s prerequisite in place. This doesn’t fix the kernel bug or rule out attacks through plain TCP.
There’s also a community XDP filter by jamilbk
. It drops incoming IPv4 packets with IP options at the network interface, before they reach the normal network stack. I read its source
, but haven’t deployed or tested it. It handles up to two VLAN tags; deeper tags and encapsulated traffic need separate consideration. Treat it as another temporary filter, not a complete fix.
The filter’s author also warns about NetLabel/CIPSO configurations , where the kernel can add IP options itself. I haven’t reproduced that path. Don’t assume filtering incoming IP options fully covers those hosts. A patched kernel is still the fix.