CVE-2026-64024

9.4

Linux · Kernel

A stale per-CPU variable leak in the Linux kernel TCP stack allows for TCP Initial Sequence Number (ISN) prediction, potentially facilitating session hijacking or data injection.

Executive summary

A critical vulnerability in the Linux kernel TCP implementation enables attackers to predict Initial Sequence Numbers, posing a severe risk of unauthorized session interception or data manipulation.

Vulnerability

The vulnerability exists due to a race condition where a per-CPU variable used for tracking TCP ISNs is not correctly cleared during packet drop events. An unauthenticated remote attacker can exploit this predictable ISN behavior to successfully spoof or hijack TCP connections.

Business impact

The exploitation of this flaw carries significant business risk, as it permits attackers to bypass standard TCP security protections to inject malicious data or intercept sensitive communications between hosts. Given the CVSS score of 9.4, this vulnerability is classified as Critical, reflecting the ease of remote exploitation and the high impact on the confidentiality and integrity of network traffic. Successful exploitation could lead to full session compromise, potentially exposing proprietary data or allowing for unauthorized administrative actions.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.34, 7.0.11, or a later stable release to incorporate the necessary fix which restores ISN tracking to the socket buffer control block.

Proactive Monitoring: Monitor network traffic for unusual TCP connection patterns, such as a high volume of unexpected resets or anomalous sequence number increments that may indicate attempted ISN prediction attacks.

Compensating Controls: Deploy network intrusion detection systems configured to identify abnormal TCP handshake patterns and ensure that firewalls are configured to drop malformed or suspicious packets that could trigger the underlying drop paths.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Due to the critical severity and the potential for network-wide impact, administrators should prioritize the deployment of the patched kernel versions across all affected systems. Failure to address this vulnerability increases the risk of sophisticated session hijacking attacks, making immediate patching the only reliable method to eliminate the exposure.

More Linux CVEs

Sources