Linux Kernel TCP Flaw CVE-2026-98432 Explained: 9.8 Bug, AI-Built Root Exploit and the Ubuntu–RHEL Patch Gap
Illustrative image: Tux, the Linux mascot. The flaw is in the Linux kernel's TCP code, not a product — there is no product photograph for a kernel bug. Image: Wikimedia Commons / Larry Ewing, Simon Budig, Garrett LeSage, CC0.
TL;DR — Linux kernel TCP flaw CVE-2026-98432 explained in one line: a use-after-free race in IPv4 TCP connection handling, rated 9.8 by the kernel's own CVE team, that Anthropic's AI model turned into a remote root exploit in the lab. Upstream kernels are fixed, but Ubuntu and RHEL had released no fixed kernel package as of 30 October 2026 — check your distribution before assuming you are safe.
📌 KEY HIGHLIGHTS
- The flaw: CVE-2026-98432, a use-after-free race in the IPv4 TCP handshake, present in every kernel since Linux 4.4. IPv6 is not affected.
- The score split: the kernel's CVE team rates it 9.8 Critical; Red Hat's pages show 5.9 and 8.1, Amazon 7.0, SUSE and Oracle 8.1. The disagreement is about how hard the race is to win, not whether the bug exists.
- The exploit: Anthropic's unreleased Claude research model built a remote root chain against servers with a multipath TCP listener — 48 minutes to leak a kernel address, 5 more to run a command as root. Lab work only; the code was not published.
- The patch gap: Debian, Oracle, Amazon and SUSE have shipped fixed kernels for at least some releases; Ubuntu and RHEL had none as of 30 October 2026.
- The status: no attacks in the wild have been reported, and the flaw is NOT in CISA's Known Exploited Vulnerabilities catalog as of 30 October 2026.
Linux kernel TCP flaw CVE-2026-98432 explained: how the bug works
The bug lives in the code that sets up a new IPv4 TCP connection. When a connection completes, the kernel hands the IP options stored with the pending request — things like Record Route or Timestamp options — to the new socket without copying them. If that socket is destroyed while another processor is still using those options to answer a resent connection request, the kernel reads memory it has already freed. That is a use-after-free, and in kernel networking code it can mean leaked kernel memory, corrupted memory, or a crash.
The upstream fix, written by Eric Dumazet and crediting Anthropic researcher Xinyang Ge with the report, makes the kernel wait until other processors finish reading the options before freeing them — freeing after an RCU grace period instead of immediately. The CVE record was published on 15 October 2026, and the kernel's CVE team added the 9.8 score on 24 October. Fixed upstream kernels are 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3. The kernel team recommends updating to the latest stable kernel rather than cherry-picking the single fix. Kernel branches that reached end of life before 5.10 get no fix at all.
The AI-built exploit: 53 minutes from handshake to root
On 27 October 2026, Anthropic's Frontier Red Team published research describing how an unreleased internal Claude model, after initial prompting, built working exploit chains for Chrome, Safari, Android, Windows and Linux. The Linux chain is the most serious of the five. It works in two stages: first, the race makes the kernel send extra bytes back to the attacker, and once one reply contains a kernel address, the attacker defeats KASLR — the randomisation that hides where kernel code sits. Second, the same bug overwrites a callback pointer with a payload the attacker already placed in kernel memory, and when the kernel calls that pointer, the attacker's command runs as root.
Two honesty notes matter here. First, this was a lab demonstration, not a real-world incident: Anthropic reported every flaw to its vendor first, published no exploit code, and did not disclose the kernel version or configuration it tested. Second, the multipath TCP (MPTCP) link rests on Anthropic's post alone — neither the CVE record nor the kernel fix mentions MPTCP. The Go Security Team added on 29 October that the underlying bug is not specific to MPTCP and that systems with no MPTCP listener may be vulnerable to similar attacks. Treat MPTCP as the demonstrated target, not the boundary of the risk.
Illustrative image: server racks at NERSC. The affected systems are the Linux servers behind services like these, not the pictured hardware. Image: Wikimedia Commons, CC0.
Why the scores disagree: 9.8 versus 5.9
The kernel team's 9.8 assumes an attacker who sends a TCP connection request carrying IPv4 Record Route or Timestamp options, then resends the request to try to win the race — and rates attack complexity low because both sides of the race are attacker-induced. Red Hat's CVE page initially rated the flaw Moderate at 5.9, arguing the race is hard to win and the most likely result is a kernel crash, with memory corruption possible only in theory and no confidentiality or integrity impact demonstrated. Red Hat's machine-readable advisory file, updated 29 October, then listed it as Important at 8.1 with high confidentiality and integrity impact — the same 8.1 Oracle and SUSE use. The vendors' scores differ from the kernel team's on exactly one metric: attack complexity, which they rate high. Amazon scores it 7.0. Ubuntu lists it as High priority. The practical reading is simple: the bug is real and severe if won, but winning the race takes repeated attempts — which is why Anthropic's 48-minute leak time matters more than the headline score.
Which distributions have a fix
Distribution status below is as reported on 29–30 October 2026. The picture moves daily, so re-check your vendor's tracker before patching day — Ubuntu and RHEL in particular may have shipped fixes since.
| Distribution | Status (30 Oct 2026) | Fixed package / advisory |
|---|---|---|
| Debian 13 (trixie) | Fixed 16 Oct | linux 6.12.113-1 (DSA-6568-1) |
| Debian 12 (bookworm) | Fixed 17 & 22 Oct | linux 6.1.190-1 (DLA-4841-1); linux-6.12 6.12.113-1~deb12u1 (DLA-4850-1) |
| Oracle Linux (UEK) | Fixed 16 Oct | ELSA-2026-500397, ELSA-2026-500398, ELSA-2026-500399 |
| Amazon Linux 2023 | Partly fixed | kernel6.18 fixed 24 Oct; kernel6.12 fixed 29 Oct; main kernel package pending |
| SUSE | Partly fixed | SUSE Linux Micro 6.2, openSUSE Leap 16.0 fixed; SLES 15 SP7 in progress |
| Ubuntu (16.04–26.10) | No fixed kernel released | Fixes in the -proposed testing pocket for 22.04, 24.04, 26.04 — not production updates yet |
| RHEL 8, 9, 10; OpenShift 4 | Affected, no fix released | No release date given; Red Hat lists no mitigation meeting its standards |
| RHEL 7 | Not affected | No action needed |
Why it matters for World Tech readers
Almost every server on the internet runs a Linux kernel, and this flaw sits in code that runs before any application sees a connection — an attacker only needs to reach an exposed TCP service. That is what makes a kernel TCP bug different from an application bug: the blast radius is every Linux host, and the fix arrives on each distributor's timetable, not the kernel's. The October pattern is now familiar — read our Fragnesia Linux kernel flaw CISA KEV explainer, our PHP2Shell CISA KEV explainer and our Warp Panda VMware ESX flaw CISA KEV explainer for the month's other exploited flaws — but this one is not yet in CISA's exploited list, which makes it a patch-before-exploitation story rather than a clean-up story.
For readers in India, there are no India-specific victims or advisories for this flaw — the relevance is structural. Indian enterprises, cloud providers, hosting firms and outsourced IT teams run large Ubuntu and RHEL estates, and those two distributions are exactly the ones without a fixed kernel yet. If your infrastructure runs on either, this is your patch queue's top item the day the fix lands, not a routine update to batch with next month's maintenance.
Should you care?
✅ Verdict: Yes, if you run Linux servers — patch the moment your distribution ships a fixed kernel, and do not wait for an in-the-wild attack to justify it. An AI model has already shown the path from handshake to root in under an hour in the lab. If you run only a Linux desktop behind a home router, the risk is far lower, but the same rule applies: install the kernel update when it arrives.
What to do now
1. Check what you run: compare your kernel against the fixed versions above or your distribution's tracker (Ubuntu's CVE page, Red Hat's CVE page, Debian's security tracker). On Ubuntu, note that the fixed builds for 22.04, 24.04 and 26.04 sit in the -proposed testing pocket as of 29 October — running an ordinary upgrade will not install them, and -proposed is for testing, not production. 2. Patch and reboot: where a fixed package exists, install it and reboot — a kernel fix only takes effect after a restart. 3. Go programs: Go 1.24 and later request MPTCP by default for listening sockets; setting GODEBUG=multipathtcp=0 at runtime (or godebug multipathtcp=0 in go.mod at build time) disables it, but the Go team calls this a fragile mitigation — a single MPTCP listener left exposed still leaves a system vulnerable. 4. Interim network control: CIQ published a firewall rule dropping IPv4 TCP packets carrying IP options, which matches the attack's prerequisite; treat it as a holding measure, not a substitute for the kernel fix. 5. Watch, don't wait: track your vendor's tracker for the Ubuntu and RHEL releases, and re-check this post's table — it will be updated when those fixes land.
FAQs
What is CVE-2026-98432?
A use-after-free flaw in the Linux kernel's IPv4 TCP connection handling, caused by a race condition that lets the kernel read freed IP-options memory during the TCP handshake. It has existed since Linux 4.4, is rated 9.8 by the kernel's CVE team, and is fixed in upstream kernels 5.10.272 through 7.3.
Is CVE-2026-98432 being exploited in the wild?
No attacks have been reported as of 30 October 2026, and the flaw is not in CISA's Known Exploited Vulnerabilities catalog. The only working exploit known is Anthropic's lab proof of concept, whose code was not published.
Which Linux distributions have fixed CVE-2026-98432?
As of 30 October 2026, Debian, Oracle Linux (UEK), Amazon Linux 2023 (kernel6.12 and kernel6.18 packages) and SUSE (some products) have shipped fixes, while Ubuntu and RHEL have released no fixed kernel. Check your vendor's tracker, since this status changes as packages land.
Does turning off Multipath TCP protect against CVE-2026-98432?
Not fully. Anthropic's exploit targeted servers with an MPTCP listener, but the CVE record and fix do not mention MPTCP, and the Go Security Team says the bug is not specific to it. Disabling MPTCP may shrink exposure, but the real fix is a patched kernel.
Takeaway: A 9.8 kernel flaw, an AI-written path to root, and a two-speed patch rollout — the kernel is fixed, the distributions are catching up, and Ubuntu and RHEL users are still waiting. Patch the day your fix lands.
Follow World Tech on TechByCountry for tomorrow's update.
📸 Get tech in the last 24 hours on Instagram — follow @_techinlast24hrs for daily posts (9 AM–9 PM) and reels at 12:30 PM & 8:30 PM.
Sources
- The Hacker News — Linux Kernel TCP Flaw With 9.8 CVSS Score Affects Ubuntu, Red Hat and Other Distributions (30 Oct 2026)
- Ostorlab — Linux Kernel TCP Handshake Race RCE (CVE-2026-98432)
- Atlas — Linux's October 2026 TCP Use-After-Free: CVE-2026-98432
- Ubuntu CVE Tracker — CVE-2026-98432 (status as checked 30 Oct 2026)
Comments
Post a Comment