A network peer can reach the affected path before application login. The Linux CNA rates it 9.8 Critical under CVSS 3.1. Anthropic says it built a remote root exploit against servers with a multipath TCP listener.
What it allows
CVE-2026-98432 concerns TCP and IPv4 option memory in the Linux kernel. A child socket can own the same option data that another CPU is still reading while it builds a SYNACK. Freeing the child can leave that reader with a stale pointer.
The Linux CNA describes a network peer reaching this path before application authentication. Its CVSS explanation identifies possible kernel memory disclosure, memory corruption, and crashes. The published score describes the flaw's potential impact; it does not prove exploitation in the wild.
On October 27, Anthropic's Frontier Red Team described an exploit Claude wrote for this flaw. It targets Linux servers with a multipath TCP (MPTCP) listener and runs commands as root without credentials or user interaction. The chain first defeats KASLR remotely. Anthropic's proof of concept took 48 minutes to leak a kernel pointer and five more to run a command.
The Go Security Team says the bug itself is not specific to MPTCP. Go 1.24 and later enable MPTCP by default for listen sockets on Linux. The team calls disabling MPTCP per program a fragile mitigation and recommends a patched kernel.
A second case involves request-socket migration. Disabling net.ipv4.tcp_migrate_req alone is not a complete fix because the first path does not need migration. The upstream change defers memory freeing until an RCU grace period has passed.
The patch says IPv6 is not affected by the first path because that path copies options. It separately notes a related CALIPSO migration issue for another patch. That distinction must not become a claim that every IPv6 path is safe.
The upstream fix changes inet_sock_destruct() and tcp_v4_reqsk_destructor(). The CVE record names net/ipv4/af_inet.c and net/ipv4/tcp_ipv4.c as affected files. Do not infer host safety from the application version alone; the relevant code runs in the host kernel.
Who is affected
The Linux CNA lists branch-specific fixed versions 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and 7.3. Read each against its own branch rather than using one number as a universal threshold.
At the October 31, 2026 check, Ubuntu's generic linux source-package rows for 26.10, 26.04 LTS, 24.04 LTS, and 22.04 LTS remained vulnerable with fixes in progress. The listed work targets were 7.3.0-10.10, 7.0.0-43.43, 6.8.0-149.149, and 5.15.0-203.213, respectively. Those are not released-fix claims, and Ubuntu's notice search listed no security notice for this CVE.
The same source package was marked vulnerable on Ubuntu 20.04, 18.04, and 16.04. Cloud, hardware-enablement, OEM, and real-time kernels have their own rows. Check the exact package and release before deciding its status.
Debian's tracker separately lists linux 6.1.190-1 fixed for bookworm security and 6.12.113-1 fixed for trixie security. Forky and sid are also marked fixed. Those distribution revisions do not certify an Ubuntu package.
Red Hat lists the kernel in RHEL 8, 9, and 10 as affected, with no released fix at the October 31 check. Its CVE page now rates the flaw Critical, with a preliminary CVSS 3.1 score of 9.8 that matches the CNA. CIQ listed no patched kernel for its RLC Pro variants on October 30.
Veeam's own KB4966 impact statement, published 6 November 2026, lists which Veeam products include a Linux kernel and are affected until each gets the fix. It names Veeam Software Appliance 13.1, Veeam Infrastructure Appliance 13.1, and the workers its hypervisor plug-ins deploy. It also names the Linux-based helper appliances in Veeam Backup & Replication 13.1 on Windows and in version 12.3, plus its plug-in appliances for AWS, Google Cloud and Microsoft Azure.
Veeam says an update with the fix has been in its own repository for Veeam Software Appliance and Veeam Infrastructure Appliance 13.1 since 2 November 2026, delivering kernel 5.14.0-570.60.1+27.2.el9_6_ciq. It says a private fix covers the Windows-based Veeam Backup & Replication 13.1 helper appliances, and that the Veeam Backup & Replication 12.3 private fix was still pending at publication. Veeam Kasten for Kubernetes is not affected, because its container images do not include a Linux kernel.
For the current Ubuntu matrix and host checks, use our Ubuntu kernel status and triage report. Our vulnerability management glossary explains how to keep package evidence with the risk record. The patch management entry covers rollout and verification.
This CVE was absent from CISA KEV catalog version 2026.10.30, checked October 31. Exploitation status remains unknown for this profile; KEV absence is not proof that attacks cannot occur, so keep following it through vulnerability intelligence.
A GitHub search on October 31 returned 25 public repositories for this CVE, all created on October 29 or 30. Most offer checks or mitigations. Several publish proof-of-concept or trigger code; we have not verified a working exploit.
Timeline
-
15 Oct 2026
Linux CNA publishes CVE-2026-98432.
-
27 Oct 2026
Anthropic describes a remote root exploit against MPTCP listeners.
-
29 Oct 2026
The Go Security Team says the bug is not specific to MPTCP.
-
30 Oct 2026
CIQ publishes an interim firewall rule that drops IPv4 TCP packets with IP options.
-
31 Oct 2026
This profile rechecks distribution status; Ubuntu generic kernel rows still show fixes in progress.
-
6 Nov 2026
Veeam publishes KB4966, listing affected products and a kernel fix available since 2 November.
What to do
-
Identify the Running Kernel and Package
Collect the Ubuntu release, running kernel, and installed kernel-image package. Find the exact kernel flavor in the vendor tracker. A generic kernel row does not cover every cloud or hardware-enablement build.
-
Check for a Released Distribution Fix
Distinguish an available fixed package from a vulnerable work-in-progress row. Use supported vendor updates. Do not cherry-pick a mainline commit into a production kernel merely because the upstream fix exists.
-
Block IPv4 Options Until a Fix Ships
CIQ documents an interim nftables rule that drops IPv4 TCP packets carrying IP options. Test it on one host first, because it also drops legitimate option traffic. Disabling MPTCP alone is not enough.
-
Verify the Running Result After Rollout
After the approved kernel rollout and any required reboot, record the running kernel again. Confirm the matching vendor row says fixed. Keep the check time and evidence with the patch ticket.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-98432 in Brandefense Atlas
The Atlas record of CVE-2026-98432: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What Does CVE-2026-98432 Affect?
It affects Linux kernel TCP and IPv4 option lifetime handling. The CNA lists upstream branch fixes, while each distribution tracks its own packages. Match the exact kernel package and release.
Is Exploitation in the Wild Confirmed?
Exploitation status is unknown for this profile, and CISA KEV did not list the CVE on October 31. Anthropic describes a working exploit it built. Public GitHub repositories publish proof-of-concept or trigger code; we have not verified a working exploit.
Does a Work-in-Progress Ubuntu Version Mean I Can Install the Fix?
No. Ubuntu defines that status as an affected package whose fix is being worked on. A fixed status identifies an available corrected package. Check the current row before deployment.
Is Disabling MPTCP Enough?
No. CIQ found plain TCP listeners still reachable with MPTCP off, and the Go Security Team says the bug is not specific to MPTCP. Install a fixed kernel when your vendor ships one.
Does CVE-2026-98432 Affect Veeam Backup Products?
Veeam's own KB4966 advisory says several of its products include a Linux kernel and are affected until they get the fix or a private patch. It names Veeam Software Appliance 13.1, Veeam Infrastructure Appliance 13.1 and related helper appliances, and says Veeam Kasten for Kubernetes is not affected.
Sources
- CVE-2026-98432Ubuntu
- CVE-2026-98432 Linux CNA RecordCVE Program / Linux CNA
- IPv4 RCU Memory-Lifetime FixLinux kernel
- CVE Statuses and Security UpdatesUbuntu
- CVE-2026-98432 Package StatusDebian Security Tracker
- Known Exploited Vulnerabilities CatalogCISA
- Discovering and Exploiting Vulnerabilities in Critical, Real-World Software With ClaudeAnthropic
- Mitigating CVE-2026-98432 on Rocky Linux 8, 9, 10, and LTS VariantsCIQ
- KB4966: CVE-2026-98432 Impact StatementVeeam Software