Threat researchCisent
A Linux kernel flaw now has an exploit, and Go programs open the door to it by default
The attack described takes over a server listening with MPTCP as root, and recent Go programs listen that way without anyone asking.

On October 29, 2026, the Go security team warned people running Go programs on Linux about a kernel flaw, CVE-2026-98432.1 According to the notice, an AI lab described an exploit that runs code remotely on a server listening with Multipath TCP (MPTCP).1 And since Go 1.24, Go programs listen with MPTCP by default on Linux.1
What it is
It’s a race in the kernel’s IPv4 TCP stack. When it accepts a connection, the kernel hands the new socket the IPv4 options that came with the request, without copying them. If a retransmitted SYN arrives at that moment, the kernel can keep reading them to build its reply, the SYN-ACK, even after that socket has been freed.2 It’s a use-after-free in ip_options_build(), and the same can happen when the kernel migrates pending connections from one socket to another.2
The official record, from the kernel’s CVE team, scores it 9.8 out of 10: it’s attacked over the network, with no credentials and no user interaction.2 It affects kernels since version 4.4.2 Red Hat gives it the same score and rates it critical.3
The exploit
The lab that described it says the exploit was written by its AI model, and that it runs commands as root, without credentials, on a Linux server listening with MPTCP.4 There are no reports of the flaw being exploited,4 and the US agency CISA doesn’t have it in its catalog of exploited vulnerabilities.5
The Go team warns that the flaw isn’t specific to MPTCP: a server that doesn’t use it could fall to similar attacks.1
Why Go matters
MPTCP is a TCP extension for using several network paths at once, and since Go 1.24, Go programs turn it on by default on Linux when they open a port.1 That’s why the Go team published how to switch it off in Go programs, while warning that doing so is fragile: a single exposed MPTCP service is enough to leave the system vulnerable.1
What to do
- Update the kernel. That’s what the Go team recommends.1 The fixed versions 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.2
- Check what your distribution says, because not all of them have the patch:
- Debian has shipped it: in bookworm, with 6.1.190-1 (DLA-4841-1) or 6.12.113-1~deb12u1 (DLA-4850-1), and in trixie, with 6.12.113-1 (DSA-6568-1).6
- Ubuntu rates it high priority, and as of October 30 had the patch in progress for its 22.04, 24.04, 26.04 and 26.10 releases.7
- Red Hat, as of October 30, had no fixed kernels for RHEL 8, 9 or 10, and says no mitigation meets its criteria.3
- If you can’t update yet, the oss-security list proposed switching MPTCP off: in each Go program, with
GODEBUG=multipathtcp=0,1 or system-wide, withsysctl -w net.mptcp.enabled=0.8 It has two limits: it affects programs that use MPTCP,8 and it assumes every attack goes through MPTCP, when the flaw isn’t specific to it.1
What we don’t know yet
Where Cisent comes in
The attack that was shown needs an MPTCP service within the attacker’s reach, and a Go program can open one without anyone asking for it.1
Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the admin panel exposed on a server nobody watches, the service published by mistake, the insecure configuration. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.
Sources
Go security team, “Protecting against CVE-2026-98432 when using Go programs”, golang-announce, October 29, 2026, forwarded to the oss-security list. https://www.openwall.com/lists/oss-security/2026/10/30/1↩︎
CVE Program, “CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period”, published October 15, 2026 and updated October 30, 2026. https://www.cve.org/CVERecord?id=CVE-2026-98432↩︎
Red Hat, “CVE-2026-98432”, updated October 30, 2026. https://access.redhat.com/security/cve/CVE-2026-98432↩︎
Daily CyberSecurity, “Linux Kernel CVE-2026-98432 Flaw Enables Remote Root”, October 30, 2026. https://securityonline.info/linux-kernel-cve-2026-98432/↩︎
CISA, “Known Exploited Vulnerabilities Catalog”, checked October 30, 2026. https://www.cisa.gov/known-exploited-vulnerabilities-catalog↩︎
Debian Security Tracker, “CVE-2026-98432”, checked October 30, 2026. https://security-tracker.debian.org/tracker/CVE-2026-98432↩︎
Ubuntu, “CVE-2026-98432”, updated October 30, 2026. https://ubuntu.com/security/CVE-2026-98432↩︎
John Haxby, “Re: Protecting against CVE-2026-98432 when using Go programs”, oss-security, October 30, 2026. https://www.openwall.com/lists/oss-security/2026/10/30/6↩︎