Red Hat has released patched kernels for a critical Linux vulnerability affecting IPv4 TCP handling, while Ubuntu has published fixes for its newer long-term-support releases in an opt-in testing channel rather than through standard updates. For businesses running Linux servers, cloud instances, appliances, or managed hosting environments, the development highlights the operational importance of kernel patch management and exposure monitoring.

What happened

The flaw is tracked as CVE-2026-98432 and has been described as a use-after-free vulnerability in the Linux kernel's IPv4 TCP code. According to the source, the issue can be triggered remotely by an unauthenticated attacker and has been rated 9.8, indicating potentially severe impact if exploitation is possible in a given environment.

Red Hat has made fixed kernels available for Red Hat Enterprise Linux 8, 9, and 10. Ubuntu, meanwhile, has released fixes for its three newest LTS versions in its testing channel. Based on the source provided, those Ubuntu fixes were not yet part of regular stable updates at the time of publication, and no date had been given for that broader rollout.

The source indicates patch availability status, but businesses should verify their exact kernel package versions, distribution advisories, and support channels before assuming systems are protected.

Why it matters for European businesses

This is not just a technical issue for Linux administrators. Many European businesses rely on Linux indirectly through cloud servers, e-commerce platforms, SaaS infrastructure, VPN gateways, container hosts, virtual machines, web hosting environments, and network appliances. A remotely reachable kernel flaw in TCP processing can raise concerns for internet-facing services because TCP is fundamental to web and application traffic.

For SMEs, the practical risk depends on exposure. Systems that accept network traffic from the internet, partners, customers, or untrusted internal segments may need urgent review. Even where exploitation details are limited or not public, security teams typically treat remotely reachable kernel flaws as high priority because successful exploitation could affect service availability, confidentiality, or system integrity.

The timing difference between vendors also matters operationally. Businesses using Red Hat-supported environments may be able to move directly to vendor-supplied fixes, while Ubuntu users may need to decide whether to deploy testing-channel patches, wait for general release updates, or apply compensating controls in the meantime. That creates a risk-management decision rather than a simple update task.

Who may be affected

• Companies running Red Hat Enterprise Linux 8, 9, or 10 on servers, cloud instances, or business applications
• Businesses using Ubuntu LTS for production workloads, especially public-facing systems
• E-commerce platforms relying on Linux-based hosting, load balancers, or application servers
• Managed service providers and digital agencies responsible for client infrastructure and maintenance
• IT and DevOps teams operating Kubernetes nodes, container hosts, virtual machines, and hybrid cloud estates
• Regulated organisations that need documented vulnerability handling and patch governance

Businesses may also be affected even if they do not manage Linux directly, because hosting providers, software vendors, and appliance manufacturers often embed Linux into their platforms.

What companies should consider

• Identify exposure quickly. Build or review an inventory of Linux systems, especially internet-facing hosts and business-critical workloads.
• Check vendor advisories. Confirm whether your exact distribution, version, and support tier are affected and whether patched kernel packages are available.
• Prioritise based on risk. Public-facing servers, multi-tenant environments, and systems handling sensitive data should usually be reviewed first.
• Plan kernel update windows. Kernel patches generally require careful change management and often a reboot, so businesses should assess maintenance timing and resilience requirements.
• Review temporary mitigations. If a stable vendor fix is not yet available for your environment, consider network exposure reduction, segmentation, stricter access controls, and enhanced monitoring where appropriate.
• Coordinate with providers. If workloads are hosted by a cloud, SaaS, or managed infrastructure partner, ask for their remediation status rather than assuming patching is automatic.
• Document actions. For regulated or security-mature organisations, record patch decisions, compensating controls, and remediation timelines.

At this stage, the key business issue is patch readiness and infrastructure visibility. Companies do not need to wait for signs of active compromise to review affected Linux assets and update plans.