SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

Linux TCP flaw still unpatched in Ubuntu and RHEL

CVE-2026-98432 rated 9.8 allows remote root command execution. Amazon Linux and SUSE patched, Ubuntu and RHEL have not released a fixed kernel as of October 29.

AutomushPublished 2 min readSource: The Hacker News

On October 27, Anthropic reported a flaw in the Linux kernel TCP code, CVE-2026-98432, for which its AI model wrote a working exploit. The flaw received a 9.8 out of 10 CVSS rating from the kernel CVE team. As of October 29, Ubuntu and Red Hat Enterprise Linux have not released a patched kernel, while Amazon Linux, Oracle Linux, SUSE and Debian have already published fixes for some of their kernels.

What actually happened

The flaw allows a remote attacker with no credentials to execute commands as root on Linux servers running a multipath TCP listener. This is not a theoretical weakness: Anthropic demonstrated a working exploit written by an AI model. The flaw affects distributions common in Israeli organisations, especially Ubuntu and RHEL which are used in many production environments.

Vendors responded at different speeds. Amazon Linux, Oracle Linux, SUSE and Debian have already released patches for some kernels. Ubuntu and RHEL, the two most common distributions in enterprise environments, have not published a patched kernel five days after disclosure.

Why it matters beyond the headline

Most organisations do not know whether multipath TCP is enabled on their servers. It is a feature used to manage multiple network paths in parallel, but it is not active by default in most installations. The problem is that if it is active, the exposure is complete: an attacker can run any command with root privileges.

For systems running under banking or other regulatory standards, this is not just a technical risk. It is a security incident that must be handled in a documented manner: check, decision, action and documentation. Failure to address a known critical vulnerability can be considered a governance failure.

What to do this week

Run sysctl net.mptcp.enabled on every Linux server running production systems. If the answer is 1, multipath TCP is active. If you are not using it explicitly, disable it with sysctl -w net.mptcp.enabled=0 and add net.mptcp.enabled=0 to /etc/sysctl.conf so the setting persists.

If you use Amazon Linux, Oracle Linux, SUSE or Debian, check whether the patch is available for your kernel version and schedule an update. If you are on Ubuntu or RHEL, you will need to decide: wait for an official patch while disabling multipath TCP, or consider a temporary move to a distribution that has already patched. For organisations running managed automation systems in controlled environments, this is the time to verify that your provider is handling this proactively.

Sources

Frequently asked questions

How do I know if multipath TCP is enabled on my servers?

Run `sysctl net.mptcp.enabled` in a terminal. If the answer is 1, the feature is active. If the answer is 0 or the parameter does not exist, you are not exposed to this flaw.

Will disabling multipath TCP break anything in my systems?

No, unless you have explicitly configured use of multipath TCP for managing multiple network paths. Most organisations do not use this feature, and disabling it will not affect normal operation.

Related guides

To the blog

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now