Red Hat released Critical kernel errata on 11-01: RHEL 8.10 kernel-4.18.0-553.182.1.el8_10 (RHSA-2026:93414; RT kernel in RHSA-2026:93415), RHEL 9.8 5.14.0-687.64.1.el9_8 (RHSA-2026:93412) and RHEL 10.2 6.12.0-211.72.1.el10_2 (RHSA-2026:93413). Third-party trackers report AlmaLinux and Oracle RHCK builds landing on 11-02. Red Hat's bulletin RHSB-2026-016 says OpenShift 4 (RHCOS nodes) is affected, interim guidance is "being evaluated", and "Multipath TCP is not a required condition for this flawβ¦ nodes in their default configuration, where MPTCP is disabled, remain affected." It publishes a stopgap nftables table that drops inbound IPv4 TCP packets carrying IP options (ip protocol tcp ip hdrlength > 5 counter drop, hook input, priority -310). Red Hat says the rule "reduces exposureβ¦ but cannot fully prevent it", and that on OpenShift it doesn't filter pod-to-pod SDN traffic. Ubuntu's 11-02 post: fixed linux packages are in -proposed for 22.04 (5.15.0-203.213), 24.04 (6.8.0-149.149) and 26.04 (7.0.0-43.43), and fixed in 26.10 (7.3.0-10.10). Ubuntu will move them to -updates after testing on more than 2,000 certified machines. 16.04 to 20.04 fixes are pending (Ubuntu Pro). Ubuntu also says MPTCP-disabling mitigations exist only because Anthropic's unreleased exploit uses MPTCP, and that "security updates are the only appropriate mitigation". Cloud and HWE kernels (linux-aws, linux-gcp, β¦) each have their own tracker rows.
apt install -t <codename>-proposed path) or wait for -updates. Until a node is patched, Red Hat's IP-options rule is the vendor-backed version of the packet filter Damien Neild suggested. Keep the Go-side GODEBUG=multipathtcp=0 from 10-30, but both vendors now say plainly that it only narrows the one known exploit. EKS/GKE/AKS managed node images follow their own kernel streams, so check the cloud-kernel row, not just linux.