Vulnerabilities

Red Hat Issues Urgent Bulletin on Critical Linux Kernel TCP Flaw (CVE-2026-98432)

Red Hat rates CVE-2026-98432, a Linux kernel TCP flaw in IPv4 connection handling, as critical. Here's who is affected and how to check your kernels.

Red Hat Issues Urgent Bulletin on Critical Linux Kernel TCP Flaw (CVE-2026-98432)

On October 30, Red Hat published security bulletin RHSB-2026-016 on CVE-2026-98432, rating its impact as critical and announcing that it is speeding up work on fixes. The news here is the vendor’s bulletin. The vulnerability itself was disclosed earlier, so it should not be described as a flaw discovered overnight.

What the new bulletin adds

The issue is in how the IPv4 stack of the Linux kernel handles TCP connections. When certain operations happen in a particular order, the code can access memory that has already been freed. A remote attacker doesn’t need an account, but exploiting the bug requires precisely timed network requests.

Red Hat says the flaw could allow code execution and that a wide range of services accepting TCP connections are exposed. A separate analysis by BleepingComputer describes a demonstration of remote command execution with root privileges on a server with Multipath TCP (MPTCP) enabled. That does not mean the same result has been shown for every Linux configuration.

The October 30 report cited here contains no confirmed reports of this vulnerability being exploited in real-world attacks. Even so, the bulletin calls for action from administrators, because the flaw is in kernel code that handles network traffic.

Who is affected

Red Hat lists RHEL 8, 9 and 10, as well as OpenShift Container Platform. Products built on the same kernel also need to be checked. Patch availability has to be confirmed for each distribution, version and package. A fix released for one distribution does not protect the others.

Disabling MPTCP alone does not remove the bug, because the vulnerability also affects standard TCP handling. Limiting access to services can reduce exposure, but it is not a substitute for patching.

What to do now

  • Inventory your servers and check which kernel versions are actually running.
  • Check the patch status in each distribution vendor’s advisory.
  • Restrict connections to services that don’t need to be publicly reachable.
  • After updating, confirm that the patched kernel is running, including any required reboot.

SecurHUB’s take

A new vendor bulletin can change how urgently you need to deal with a vulnerability that was already known. Security management and audits help you map an advisory to specific servers and confirm that the updates you deployed actually work.

Sources: Red Hat, BleepingComputer

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk