Skip to content
Linux TCP CVE-2026-99288: Verify the Kernel Fix

Linux TCP CVE-2026-99288: Verify the Kernel Fix

November 17, 2026

CVE-2026-99288 is a Linux TCP socket lookup race that can cause a kernel panic. The Linux CNA announcement, published November 10, 2026, describes the crash. Red Hat rates it Important and describes unauthenticated remote denial of service; Ubuntu assigns Medium priority.

Red Hat explicitly rules out arbitrary code execution in its statement, while its preliminary CVSS fields conflict with that statement. Read each assessment in its product context. The NVD detail link is also referenced by Red Hat and Debian.

Prioritize hosts whose TCP listeners accept untrusted traffic. Install a supported kernel that your supplier confirms fixes this CVE, then verify that the host has booted into it. Distribution backports make a bare upstream version comparison unreliable.

What fails in the socket lookup

TCP uses a hash table to find sockets without locking each lookup. Its allocator permits socket memory to be reused while an older reader still holds the address. If a replacement socket has the same connection tuple, the reader can take a reference to it before it has entered the hash table. The reported SYN-cookie request socket had a NULL rsk_listener; tcp_v4_rcv() dereferenced that listener and the kernel panicked. The CNA records this reproduction; no exploit was run for this article.

The upstream fix checks hash membership after taking a reference in both IPv4 and IPv6 lookups. In Linux 6.12.117, __inet_lookup_established() in net/ipv4/inet_hashtables.c rejects an unhashed or changed socket:

if (unlikely(hlist_nulls_unhashed_lockless(&sk->sk_nulls_node) ||
             !inet_match(net, sk, acookie, ports, dif,
                         sdif))) {
    sock_gen_put(sk);
    goto begin;
}

Dropping the reference and restarting avoids returning that object. The patch also changes failure cleanup in SYN-cookie, Fast Open and request-migration paths to release references through reqsk_put(). Directly freeing a request would ignore a reference temporarily held by a racing lookup. A backport needs the applicable lifetime fixes as well as the lookup check.

Match the kernel to a fixed branch

The CNA dates introduction to Linux 4.4, when request sockets were added to the established hash table to reduce listener lock contention. Source checks covered that 4.3/4.4 boundary and these stable-release pairs:

BranchInspected release without the lookup guardFixed release and patch
6.126.12.1166.12.117
6.186.18.626.18.63
7.37.3.37.3.4

The CNA announcement lists these fixes by branch. Each fixed version applies to its named branch. Other branches and vendor builds require their own assessment. For an upstream kernel, use a supported release containing the complete fix.

Vendor status checked November 17, 2026:

DistributionPublished status
Debian bookwormlinux source fixed in 6.1.192-1; the current security row lists 6.1.192-2 as fixed.
Debian trixielinux source fixed in 6.12.117-1.
Debian sid / forkySid 7.3.4-1 is fixed; forky 7.2.15-1 remains vulnerable.
UbuntuThe linux package for 26.10, 26.04 LTS, 24.04 LTS, 22.04 LTS and 20.04 LTS is marked “Needs evaluation” on the page updated November 11. Check the exact kernel flavor separately.

The Debian tracker reports source-package revisions; map the installed binary kernel package to its source revision. Ubuntu’s package matrix distinguishes generic, HWE and cloud kernels. “Needs evaluation” provides neither a fixed-package claim nor an unaffected verdict. An exact fixed RHEL package was not verified here; obtain the applicable erratum through Red Hat’s CVE page or support channel.

Collect evidence from the host

These read-only commands were run in a Linux container on November 17. They require no root access, create no files and need no cleanup:

uname -sr
. /etc/os-release
printf 'OS=%s\n' "$PRETTY_NAME"
systemd-detect-virt --container
sysctl net.ipv4.tcp_syncookies

Observed output:

Linux 6.18.57
OS=Debian GNU/Linux 13 (trixie)
container-other
net.ipv4.tcp_syncookies = 1

The container runs Debian userspace on the reported kernel. The version alone cannot establish whether its supplier backported the fix. The SYN-cookie value describes this network namespace; it does not test the race or prove the host’s patch status.

The Debian-family package inventory returned an error:

dpkg-query -W -f='${binary:Package}\t${Version}\n' 'linux-image-*'

Observed error output:

dpkg-query: no packages found matching linux-image-*

The command exited with status 1. The container’s package database contains no matching kernel packages, so it cannot verify the host kernel’s provenance. Repeat the inventory on the machine or VM supplying the kernel. Record the installed kernel’s full package revision and supplier advisory, and match them to the running release. Updating only a container image leaves the shared host kernel unchanged.

Boot and check the patched kernel

Test the vendor’s update on a representative host, then install it through the supported package channel and reboot into the replacement. Recheck the running release against the fixed package and retain the advisory identifying its backport. If a livepatch service is used, require explicit coverage for this CVE and confirmation that the patch is active. Ordinary TCP health checks can verify service recovery; they cannot prove a timing-dependent flaw is absent. No kernel update, livepatch or crash reproduction was tested here.

If patching must wait, review Red Hat’s mitigation guidance with the host and network owners. Disabling SYN cookies reduces SYN-flood protection, and the setting is per network namespace. Changing receive queues and packet steering also needs deployment-specific testing. Prefer a verified kernel fix over an untested networking change.

Acknowledgements

This post was created with assistance from AI.

Last updated on