Cybersecurity
Red Hat patches Linux TCP flaw, Ubuntu tests fixes
Red Hat shipped fixes for a Linux kernel IPv4 TCP use-after-free that could permit remote code execution, while Canonical kept Ubuntu updates for three LTS releases in its testing channel.
- Red Hat and Canonical said CVE-2026-98432 could let a remote attacker without credentials reach remote code execution through the Linux kernel's IPv4 TCP path.
- Red Hat released fixed kernels for Red Hat Enterprise Linux 8, 9 and 10 on 1 November, while Canonical said on 2 November that Ubuntu 22.04 LTS, 24.04 LTS and 26.04 LTS fixes were still in -proposed.
- The Linux kernel CVE team rated the flaw 9.8 out of 10, and Red Hat raised its own score from 5.9 to 9.8 and classed it as Critical.
- No vendor, CERT or kernel CVE team had reported exploitation, and CISA had not listed the issue in its Known Exploited Vulnerabilities catalogue as of 30 October.
- Anthropic said on 27 October that an unreleased internal Claude research model had built a remote root exploit in a proof of concept, while public GitHub code only triggered the race and checked for freed memory being echoed back.
Red Hat said it had issued RHSA-2026:93414 for Red Hat Enterprise Linux 8, RHSA-2026:93412 for Red Hat Enterprise Linux 9 and RHSA-2026:93413 for Red Hat Enterprise Linux 10 on 1 November. Canonical said on 2 November that fixes for Ubuntu 22.04 LTS, 24.04 LTS and 26.04 LTS were in its proposed pocket, and administrators would need to reboot after installing them.
The issue was tracked as CVE-2026-98432 in the Linux kernel's IPv4 TCP code. Red Hat and Canonical said a remote attacker without credentials could use it for code execution, and the bug had existed since Linux 4.4 before the upstream correction landed in October.
The kernel passed IP options from an incoming IPv4 TCP connection into a new socket without copying them first. If a client repeated the connection request while another processor still read those options, the kernel could access memory after freeing it; the trigger involved IPv4 Record Route or Timestamp options on a listening port.
Red Hat published an nftables rule on 30 October that dropped inbound IPv4 TCP packets carrying IP options, but it said the rule could not fully stop exploitation and might break workloads that relied on those options. The CIQ kernel team said the filter only applied on the host where it was loaded, and Canonical said disabling Multipath TCP alone was not enough.
No vendor, CERT or the kernel CVE team had reported attacks, and the issue was not in CISA's exploited-vulnerability catalogue as of 30 October. Anthropic said on 27 October that an internal Claude research model had produced a remote root exploit for Linux servers with an MPTCP listener, while proof-only code on GitHub merely detected the race and did not execute code.
Named in this story
Companies
- Red Hat
- issued fixed kernels and raised its severity rating
- Canonical
- said Ubuntu fixes were in its proposed testing pocket
- Anthropic
- said an internal research model built a root exploit proof of concept
- SUSE
- had shipped fixes in October
Organisations
- Linux kernel CVE team
- rated the flaw 9.8 out of 10
- Ubuntu Security Team
- said security updates were the only appropriate mitigation
- CIQ kernel team
- said the nftables filter could be bypassed between containers
- Debian
- had shipped fixes in October
Governments and agencies
- CISA
- had not listed the flaw in its Known Exploited Vulnerabilities catalogue
Products and systems
- Linux kernel
- contained the vulnerable IPv4 TCP path
- Red Hat Enterprise Linux 8
- received a fixed kernel on 1 November
- Red Hat Enterprise Linux 9
- received a fixed kernel on 1 November
- Red Hat Enterprise Linux 10
- received a fixed kernel on 1 November
- Ubuntu 22.04 LTS
- had fixes in the proposed pocket
- Ubuntu 24.04 LTS
- had fixes in the proposed pocket
- Ubuntu 26.04 LTS
- had fixes in the proposed pocket
- Amazon Linux
- said the flaw could mainly cause a crash and possible memory corruption
- Oracle Linux
- had shipped fixes in October
How the source tells it
The article was written as a technical security update with no strong emotive framing.
No emotive framing was found in the original.