Status checked: October 31, 2026.
CVE-2026-98432 is a Linux kernel use-after-free reachable through TCP and IPv4 options. Ubuntu’s entry, last updated on October 30, still marks several kernel packages vulnerable with fixes in progress. The key distinction is between a fix in upstream Linux and a fixed package for your exact Ubuntu release and kernel flavor.
The Linux CNA record was published on October 15. This is a current package-status check, not a claim that the flaw was first disclosed today. Our CVE-2026-98432 vulnerability profile keeps the technical scope and branch fixes together.
Ubuntu’s Package Rows Still Show Work in Progress
The Ubuntu CVE tracker lists the following state for the source package named linux. The version strings are work targets shown beside vulnerable rows. They must not be presented as available security updates or as proof that a host is patched.
- Affected
The same linux row marks Ubuntu 20.04, 18.04, and 16.04 vulnerable. Other kernel flavors have separate rows, including cloud, hardware enablement, OEM, Raspberry Pi, and real-time packages. A result for the generic source package does not certify those other builds.
Ubuntu’s status definitions make the distinction explicit: work in progress means the team is working on a fix for an affected package. Fixed means a corrected version is available. Read the package and release together. An ignored or absent package row is not interchangeable with a fixed one.
Upstream Fixes Do Not Identify an Ubuntu Package
The Linux CNA record 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. These are upstream version entries, not one universal minimum for every kernel. Distribution backports need their own package evidence.
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. Ubuntu’s notice search listed no security notice for this CVE on the same day.
The Debian security tracker shows why that matters. It lists linux 6.1.190-1 as fixed for bookworm security and 6.12.113-1 for trixie security. Forky and sid are marked fixed too. Those Debian package results do not establish the status of an Ubuntu kernel with a different package name and revision.
Keep three fields in the patch record: the running kernel, its installed package, and the matching vendor status. A scanner’s upstream version comparison is useful input. It is not enough to close the ticket when the distribution has backported code or still lists the package as vulnerable.
What Does Veeam’s KB4966 Advisory Add About This Flaw?
Update, 9 November 2026. Veeam’s own KB4966 impact statement, published 6 November, lists which of its 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.
The TCP Race Happens Before Application Login
The CNA’s scoring explanation describes a network peer sending a TCP SYN with IPv4 Record Route or Timestamp options. The kernel stores those options with a connection request. A retransmitted SYN can make one CPU build a SYNACK while another path frees the child socket and its options.
The remaining reader can then use freed memory while building the packet. The CNA describes possible kernel memory disclosure, memory corruption, and crashes. That is a serious remote attack surface. It does not by itself prove that a reliable exploit is being used against deployed systems.
The upstream Linux change replaces immediate freeing in two paths with freeing after an RCU grace period. RCU lets readers finish before the memory is released. A second case involves request-socket migration, including configurations using net.ipv4.tcp_migrate_req=1.
That migration setting is not a requirement for the first TCP/IPv4 path. Turning it off is therefore not a complete fix. The patch also distinguishes IPv6: the first path duplicates options there, while a related CALIPSO migration issue is left to a separate patch. Do not turn that distinction into an all-IPv6 safety claim.
Disabling MPTCP Alone Does Not Close the Flaw
On October 27, Anthropic’s Frontier Red Team described an exploit Claude wrote for this CVE. It sends packets to Linux servers with a multipath TCP (MPTCP) listener and runs commands as root, with no 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 minutes to run a command.
The Go Security Team says the demonstrated exploit needs an MPTCP listener, but the underlying bug is not specific to MPTCP. Since Go 1.24, Go programs enable MPTCP by default for listen sockets on Linux. Setting GODEBUG=multipathtcp=0 turns that default off, yet the team calls this fragile and recommends a patched kernel.
CIQ’s advisory goes further. In its tests, a plain TCP listener still answered a SYN carrying a Record Route option with net.mptcp.enabled=0. Its interim rule instead drops every IPv4 TCP packet that carries IP options before the TCP stack sees it.
sudo nft add table inet ciq_cve_2026_98432
sudo nft add chain inet ciq_cve_2026_98432 prerouting "{ type filter hook prerouting priority -300; policy accept; }"
sudo nft add rule inet ciq_cve_2026_98432 prerouting ip hdrlength gt 5 meta l4proto tcp counter drop
CIQ says the rule is not a complete fix and also drops legitimate traffic with IP options, so test it on one host first. It listed no patched kernel for its RLC Pro variants on October 30. Remove the rule once a fixed kernel is running.
Rui Sousa’s October 31 oss-security post suggests init_on_free=1 as additional hardening, not a fix, because it zeroes freed memory that a use-after-free read could return. It says AlmaLinux 9 and 10 kernels ship with it off and cites roughly 1 to 5% cost on workloads heavy in memory frees. It also notes that same-host container traffic can bypass a packet filter.
Keep the Two Scores and Exploitation Evidence Separate
Ubuntu displays 9.8 Critical under CVSS 3.1 and 8.3 High under CVSS 4.0. Its own priority is High. The Linux CNA record supplies the 9.8 vector below. These are different scoring systems and a vendor priority, not three competing reports of active attacks.
- Attack Vector
- Network AV:N
- Attack Complexity
- Low AC:L
- Privileges Required
- None PR:N
- User Interaction
- None UI:N
- Scope
- Unchanged S:U
- Confidentiality
- High C:H
- Integrity
- High I:H
- Availability
- High A:H
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H The CISA KEV catalog, version 2026.10.30, does not list this CVE. Absence from KEV is not evidence that exploitation cannot occur, so keep tracking it with vulnerability intelligence software.
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. Brandefense Blackhole recorded 29 posts naming the CVE, mostly news reposts and CVE alerts on October 29 and 30.
- Vendor exploit researchYesAnthropic describes a working remote root exploit against MPTCP listeners.2026-10-27
- Public PoC or trigger codeYes25 GitHub repositories created October 29 to 30; working exploit not verified by us.2026-10-31
- CISA KEVNot seenNot listed in catalog version 2026.10.30, checked October 31.2026-10-31
- Brandefense BlackholeYes29 posts naming the CVE, mostly news reposts and CVE alerts.2026-10-31
The public sources used here document the flaw and patch status. They do not establish an in-the-wild exploitation incident for this report. The operational decision should use reachable services, affected packages, and the cost of an outage, rather than treating a score or social post as incident proof.
Build a Host Record Before Closing the Patch Ticket
Start with the host, not the planned version in a web table. On an Ubuntu system, collect its release, running kernel, and installed kernel-image packages. The commands below are inventory steps. They do not test whether the vulnerability can be exploited.
cat /etc/os-release
uname -r
dpkg -l 'linux-image*'
- Match the package: identify its kernel flavor and find the exact release row in Ubuntu’s tracker. Keep the status and check time with the host record.
- Review reachability: find the TCP services that need to be reachable. Reduce unnecessary access through your normal network controls while the vendor fix is pending. This is exposure reduction, not a patch.
- Use supported updates: refresh package information and review the available upgrades. Do not treat a successful upgrade command as proof that this specific CVE was fixed.
- Verify the running result: after the approved kernel rollout and any required reboot, record the running kernel again. Check it against a vendor row that actually says fixed.
Ubuntu’s package-management guidance uses the following commands to refresh the package index and upgrade installed packages. Follow your change process. The Ubuntu CVE guidance advises against cherry-picking individual updates. For a flaw in Ubuntu’s own package manager, see our APT CVE-2026-109518 explainer.
sudo apt update
sudo apt upgrade
For the wider process, our patch management glossary explains rollout and verification. The Vulnerability Management 101 guide connects those actions to inventory, risk, and closure evidence. Keep this CVE open for any host whose matching package remains vulnerable or whose running result has not been verified.
For another exploited Linux kernel issue, see the CVE-2026-31431 Copy Fail profile.
Frequently Asked Questions
Is CVE-2026-98432 Already Fixed in Ubuntu?
At the October 31 check, the generic linux rows for Ubuntu 26.10, 26.04, 24.04, and 22.04 still showed vulnerable with fixes in progress. Check your exact package and release; planned versions are not released fixes.
Does Disabling TCP Request Migration Fix the Whole Issue?
No. The upstream description has a first TCP/IPv4 path that does not require request migration. Disabling the migration setting does not remove that first path.
Can I Use the Upstream Version as My Ubuntu Patch Target?
Use Ubuntu package evidence for an Ubuntu host. Upstream branch fixes and distribution package revisions are different records, and a backport may not share the upstream version string.
Is Disabling MPTCP Enough to Stop CVE-2026-98432?
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; CIQ's interim rule drops IPv4 TCP packets with IP options.
Sources
- Ubuntu: CVE-2026-98432
- Linux CNA: CVE-2026-98432
- Linux upstream fix
- Ubuntu: CVE statuses and security updates
- Debian: CVE-2026-98432 package status
- Anthropic: Discovering vulnerabilities with Claude
- CISA: Known Exploited Vulnerabilities Catalog
- CIQ: CVE-2026-98432 mitigation
- Veeam: KB4966 CVE-2026-98432 Impact Statement
