TuxCare’s November 16, 2026 roundup described different NoisyTCP patch situations across kernel families: it reported RHEL 6, RHEL 7 and CentOS 7 as unaffected; fixes for Oracle Linux UEK and selected CIQ builds; and no fixed kernel shipped for RHEL 8–10 at that point. The report is a dated snapshot, not a statement about later updates.

What NoisyTCP can do and when

NoisyTCP, tracked as CVE-2026-99288, is a race condition in Linux kernel TCP connection lookups. Under the conditions described by researcher Hyunwoo Kim, a stale lookup can encounter memory reused for a new request socket; the socket has no listener attached, and the resulting kernel panic can cause a remote denial of service. The demonstrated impact is a crash, not general-purpose remote code execution. Kim’s advisory

The described attack requires a TCP listener reachable by the attacker and receive processing across multiple contexts: at least two RX queues, or Receive Packet Steering (RPS) distributing packets across CPUs. A web or SSH service alone does not establish that the network-processing condition is present. A container does not isolate its service from a host-kernel panic because containers share the host kernel.

Check the advisory for the exact kernel package you run; a distribution name alone is not a patch status.

Patch status by kernel family on November 16

In its November 16 snapshot, TuxCare reported that RHEL 6, RHEL 7 and CentOS 7 kernels were not affected. It reported fixed Oracle Linux UEK errata ELSA-2026-500630, ELSA-2026-500631 and ELSA-2026-500632, with shipment dated November 12–13.

For CIQ commercial Rocky Linux builds, TuxCare listed RLC Pro, RLC Pro LTS, RLC Pro FIPS and SIG/Cloud Next as patched; CIQ Linux Kernel LT 6.12 was still pending in that snapshot. TuxCare also reported that no fixed kernel had shipped for RHEL 8, 9 or 10 by November 16.

Separately, TuxCare said stable kernels 6.12.117, 6.18.63 and 7.3.4 shipped with the main NoisyTCP fix. Kim dates the upstream fix commit, 4e2b3ef19e0e, to November 3, 2026. Distribution packages can include backported fixes, so an upstream version number by itself does not identify the status of a vendor build.

What server administrators should check

Check the security advisory for the exact distribution and kernel package installed, then install its fixed package and boot into that kernel. Debian and Ubuntu publish package-specific records in their security trackers, rather than one status that applies to every kernel flavor: Debian’s tracker and Ubuntu’s tracker.

Kim lists two temporary mitigations: disable SYN cookies, or limit ingress to one RX queue and disable RPS and Receive Flow Steering (RFS). Disabling SYN cookies weakens SYN-flood protection, and the setting must be applied in each network namespace. The documented command is sudo sysctl -w net.ipv4.tcp_syncookies=0. Kim’s advisory