Linux TCP flaw: check the hosts behind your store

Linux CVE-2026-98432 requires host-level checks. Review current distribution fixes and distinguish managed services from self-managed commerce servers.

SSophie Harrington3 min read

14 November: Ubuntu fixes are available for newer releases

Ubuntu’s announcement, updated on 9 November, says fixes for Ubuntu 22.04 LTS and newer are now in the archive. Its earlier instructions to enable the testing-only -proposed pocket are no longer needed. This supersedes the pending-fix status in our dated November notes below.

On our 14 November check, the CVE tracker lists these fixed versions for the main linux package:

  • Ubuntu 22.04 LTS: 5.15.0-203.213
  • Ubuntu 24.04 LTS: 6.8.0-149.149
  • Ubuntu 26.04 LTS: 7.0.0-43.43
  • Ubuntu 26.10: 7.3.0-10.10

The main packages for 20.04, 18.04 and 16.04 still show fixes in progress. Cloud, hardware-enablement and other kernel flavours have separate entries: match the actual host package rather than applying this short list to every installation.

Ubuntu says a reboot is required after installing the kernel update. Ask the hosting owner to confirm the running kernel afterwards and retest important integration jobs. An available package, an installed update and a host running the fixed kernel are three different checkpoints. The earlier mitigation discussion is not a reason to postpone an available security update.

A critical Linux networking flaw deserves a check of the servers around your store: custom apps, middleware and self-managed storefront infrastructure. CVE-2026-98432 affects the kernel’s IPv4 TCP handling, so an application-only update is not a substitute for checking the host.

Red Hat rates it Critical and describes remotely triggered memory corruption or a crash. In a separate 27 October research disclosure, Anthropic reports a working proof of concept against a Linux server with a multipath TCP listener, allowing commands to run as root without credentials. That demonstrated configuration is important; it is not evidence that every exposed Linux service has already been compromised.

Check the distribution, not just the headline

On our 2 November check, Ubuntu’s tracker still listed the main kernel packages for 22.04, 24.04, 26.04 and 26.10 as vulnerable, with fixes in progress. Red Hat’s page listed RHEL 8, 9 and 10 as affected. These are time-sensitive vendor statuses, not a permanent compatibility table.

AWS’s bulletin says fixed Amazon Linux kernel packages are available and directs self-managed EC2 and Lightsail customers to update and reboot. It separately says Lambda workloads are not affected by this exposure and require no customer action. Managed services and self-managed instances should therefore not receive the same blanket instruction.

Give the hosting owner a concrete task

Our recommendation is to list the hosts behind your custom commerce services and assign an owner to each. Ask them to confirm the distribution advisory, the fixed package and the kernel actually running after maintenance. Check critical webhooks and integration jobs after any restart, and retain the result with the maintenance record.

Where a patch is unavailable, ask the provider for its current supported mitigation. AWS describes disabling multipath TCP as an interim reduction in exposure, not a complete fix. Avoid copying an arbitrary firewall command into production without checking how it affects legitimate traffic.

This is separate from the runtime work in our Node.js patch guide. Keep host, runtime and application checks separate so that completing one does not mistakenly close the others.

4 November update: match the fix to the kernel package

Red Hat’s RHSA-2026:93415 advisory, issued on 1 November, provides a fix for CVE-2026-98432 in RHEL 8 kernel-rt packages. These are real-time kernel packages; this advisory should not be read as confirmation that every RHEL 8, 9 or 10 kernel is fixed. Red Hat says a reboot is required for this update to take effect. Match the host’s installed package and product subscription to the relevant advisory before closing the maintenance task.

On our 4 November check, Ubuntu’s tracker, last updated 3 November, still marked the main linux packages for 22.04, 24.04, 26.04 and 26.10 as vulnerable, with work in progress. A target version shown beside that status is not confirmation that the fix has been released. Check the exact kernel flavour your host uses, since cloud and hardware-enablement packages have separate entries.

ℹ️
A patched application or container image does not establish that the host kernel is fixed. Ask the hosting owner to verify the running kernel against the vendor advisory.

5 November: Ubuntu mitigation has limits

Ubuntu’s security tracker, updated 4 November, now describes filtering incoming IPv4 TCP packets that contain IP options. It explicitly says this reduces risk but does not fully prevent exploitation. The main linux packages for 22.04, 24.04, 26.04 and 26.10 still show vulnerable, with fixes in progress, on our 5 November check.

Ask the hosting owner to assess the vendor procedure against the actual firewall setup. It assumes IPv4 options are not needed and gives persistence instructions for nftables without UFW or firewalld. Connections that depend on those options can break. Containers with separate networking need separate treatment; a host rule does not automatically cover them. Keep the kernel update and running-kernel verification task open.

Filed underNews

More from News

See all →