# NoisyTCP (CVE-2026-99288): 11-Year-Old Linux Kernel TCP Race Condition Enables Remote Unauthenticated Crash

> NoisyTCP is a race condition in the Linux kernel's TCP established-socket lookup that lets a remote, unauthenticated attacker panic any host with a plain TCP listener by sending IPv4 fragments and TCP packets that are steered to different CPUs, causing a NULL rsk_listener dereference. The flaw dates to commit 079096f103fa (2015-10-03) and was fixed upstream by commit 4e2b3ef19e0e (2026-11-03). Impact is remote denial of service; no in-the-wild exploitation, public PoC, or CISA KEV listing is reported.

- **Published:** 2026-11-16T05:41:56Z
- **Last reviewed:** 2026-11-16T05:41:56Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6114
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6114.png
- **ID:** TL-2026-6114
- **Severity:** HIGH (CVSS 7.5)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 14 (3 shown free below)
- **CVEs:** CVE-2026-99288

## Description

NoisyTCP (CVE-2026-99288) was reported and patched by researcher Hyunwoo Kim (@v4bel), who published an advisory at github.com/V4bel/NoisyTCP and posted to oss-security on 2026-11-15 after the distribution embargo ended. The bug is an ABA-style race in the kernel's TCP receive path: a lookup of established connections matches on the connection 4-tuple but does not check whether the socket is still hashed. One CPU finds an existing half-open request socket while another CPU frees that request_sock and reuses the same memory for a new SYN-cookie request with the same connection details. The first CPU takes a reference on the new object, which has no listener attached, and the TCP receive path (tcp_v4_rcv) dereferences the NULL rsk_listener, producing a kernel panic. The upstream fix is titled "inet: reject unhashed sockets during established lookups".

The attacker spreads processing across receive contexts by exploiting the difference in receive hash between IPv4 fragments and ordinary TCP packets, so the racing packets land on different CPUs. Exposure requires two or more NIC receive queues, or Receive Packet Steering (RPS) distributing packets across CPUs, and a plain TCP listener (listen()). No unusual sysctls, firewall rules or special sockets are needed; default Nginx, Apache and SSH servers are reachable. In a container host a panic takes down the whole machine because the kernel is shared. A second, separate path (the 'Full child socket ABA race') could produce a remote use-after-free, but it needs several successive races and is much harder to trigger; the researcher does not claim remote code execution, and sources state it is not a TCP RCE 'at least for now'.

Reported trigger timing in the researcher's lab: about 5 seconds to 2 minutes against default configurations on QEMU/KVM virtual machines (hypervisor vCPU pausing widens the race window), and about 14 hours against a quiet bare-metal Nginx server with 8 RX queues even with a tuned PoC. The researcher holds only a very limited, lab-specific exploit for VM servers that has not been released; the GitHub repository contains the write-up only. No exploitation in the wild is reported and the CVE is not in CISA KEV (securityonline reports a 30-day EPSS of 0.2%). Severity: NVD analysis and CNA CVSS were still awaiting at time of writing; Red Hat rates it 7.5 and Oracle rates it 8.1 Important (ELSA-2026-500630 to 500632). The cvss_score recorded here is the Red Hat figure; no vector is published. CWE identifiers are analyst-assigned from the described mechanics (race condition, NULL dereference, and use-after-free for the secondary path) since no source states a CWE.

Affected: Linux kernel from the 2015 introducing commit (stated as 4.4 and later) up to 6.12.116, 6.18.62 and 7.3.3. Fixed in stable 6.12.117, 6.18.63 and 7.3.4 (released 2026-11-10) and 7.4-rc2. The 7.2 branch ended at 7.2.15 on 2026-11-01 before the fix existed; 5.10, 5.15, 6.1 and 6.6 had no fixed upstream release as of 2026-11-15. Debian patched bookworm (6.1.192-1, DLA-4906-1) and trixie (6.12.117-1, DSA-6628-1); Arch shipped linux 7.3.4.arch1-2 and linux-lts 6.18.63-3; Ubuntu 16.04 to 26.10 were 'needs evaluation'; RHEL 8/9/10 were listed affected without an erratum. Weakly ordered CPU architectures (arm64, POWER, RISC-V) additionally need upstream commit 5b5d8f351dd9. Defender notes: there are no network IOCs; detection is based on exposure checks (RX queue count, RPS masks, kernel version/changelog), unexplained kernel panics on TCP-listening hosts, and unusual IPv4 fragment traffic accompanying TCP to listeners (the last is analyst inference, not a published signature).

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1499.004 Application or System Exploitation
- T1529 System Shutdown/Reboot

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**NoisyTCP (CVE-2026-99288) Kernel Fault in TCP Receive Path (tcp_v4_rcv / rsk_listener) — Exploitation Outcome** (`TL-2026-6114-SPL-001`)

Detects the described NoisyTCP crash signature: a kernel panic, oops, KASAN use-after-free or NULL-pointer dereference logged within the same 2-minute bucket as tcp_v4_rcv / tcp_check_req / rsk_listener / inet_lookup_established frames on one host (NULL rsk_listener dereference after the established-lookup ABA race, CVE-2026-99288; the KASAN branch covers the harder 'Full child socket ABA race' use-after-free path, CWE-416, for which no RCE is claimed). Oops text is multi-line, so the search correlates lines per host per bucket. The exact oops text is unpublished and there is no network IOC, so the crash itself is the highest-fidelity signal. Requires kernel logs (syslog/journald/netconsole/kdump) forwarded to the SIEM.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1190, T1499.004, T1529
- **Data sources:** linux_syslog, kernel_log, journald, kdump
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=os sourcetype=syslog earliest=-24h ("Kernel panic" OR "NULL pointer dereference" OR "Oops:" OR "Fatal exception" OR "KASAN" OR "tcp_v4_rcv" OR "tcp_check_req" OR "rsk_listener" OR "inet_lookup_established")
| eval fault=if(match(_raw,"Kernel panic|NULL pointer dereference|Oops:|Fatal exception|KASAN: [\\w-]*use-after-free"),1,0), tcp_frame=if(match(_raw,"tcp_v4_rcv|tcp_check_req|rsk_listener|inet_lookup_established"),1,0)
| bin _time span=2m
| stats sum(fault) as fault_lines sum(tcp_frame) as tcp_frame_lines count as total_lines values(source) as sources by _time host
| where fault_lines>0 AND tcp_frame_lines>0
| table _time host fault_lines tcp_frame_lines total_lines sources
```

### Microsoft KQL

```kql
Syslog
| where TimeGenerated > ago(24h)
| extend IsFault = SyslogMessage has_any ("Kernel panic", "NULL pointer dereference", "Oops:", "Fatal exception") or SyslogMessage matches regex @"KASAN: [\w-]*use-after-free"
| extend IsTcpFrame = SyslogMessage has_any ("tcp_v4_rcv", "tcp_check_req", "rsk_listener", "inet_lookup_established")
| where IsFault or IsTcpFrame
| summarize FaultLines = countif(IsFault), TcpFrameLines = countif(IsTcpFrame), TotalLines = count(), Sample = take_any(SyslogMessage) by Computer, HostIP, bin(TimeGenerated, 2m)
| where FaultLines > 0 and TcpFrameLines > 0
| project TimeGenerated, Computer, HostIP, FaultLines, TcpFrameLines, TotalLines, Sample
```

### Sigma

```yaml
title: NoisyTCP CVE-2026-99288 Fatal Kernel Exception in Interrupt Context
id: 6b0f3a52-8c1d-4e7a-9a21-5d3c7e1f4a01
status: experimental
description: Detects a fatal kernel exception raised in interrupt (softirq) context, the panic form expected when the NoisyTCP NULL rsk_listener dereference in tcp_v4_rcv fires with panic_on_oops=1. Generic by itself; correlate with TCP-path RIP frames (see SIG-001) and with the host running a TCP listener.
references:
    - https://github.com/V4bel/NoisyTCP
    - https://access.redhat.com/security/cve/CVE-2026-99288
    - https://securityonline.info/noisytcp-vulnerability-cve-2026-99288/
author: Threadlinqs Team
date: 2026/11/16
tags:
    - attack.impact
    - attack.t1499.004
    - attack.t1529
    - attack.initial-access
    - attack.t1190
    - cve.2026.99288
logsource:
    product: linux
    service: syslog
detection:
    keywords_panic:
        - 'Kernel panic - not syncing: Fatal exception in interrupt'
        - 'Kernel panic - not syncing: Fatal exception'
    condition: keywords_panic
falsepositives:
    - Hardware faults, driver bugs or other kernel defects that panic in interrupt context
    - Deliberate crash tests (sysrq-c, kdump validation)
level: high

```

**Known false positives:**

- Unrelated kernel/driver bugs or hardware faults that crash in the network receive path
- Planned crash-dump tests (echo c > /proc/sysrq-trigger) on TCP-listening hosts

**Tuning notes:** Adjust index/sourcetype to where kernel logs land (e.g. linux_messages_syslog, journald, netconsole). Hosts without kdump/pstore/netconsole lose the oops on panic, so enable remote kernel logging. Suppress hosts in planned crash-test windows. Prioritise internet-facing multi-RX-queue/RPS hosts running nginx/apache/sshd. Kernels containing fix commit 4e2b3ef19e0e should not crash this way.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- NoisyTCP (CVE-2026-99288) Multi-Host Kernel Panic Burst — Fleet-Wide Remote DoS (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Mitigation / Posture Change And Exposure Checks — tcp_syncookies=0, RX Queue Reduction, RPS/RFS, ethtool -l (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Exposure — Hosts Booted On Affected Upstream Kernel Versions (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Kernel Oops Or KASAN Report In TCP Established-Lookup Path (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) kdump Vmcore Saved After Kernel Crash (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Post-Crash Recovery Artifacts — Unclean Journal Or Filesystem Recovery (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Unclean Host Reboot After Kernel Crash — Impact (locked: unlock with TL Creds)
- NoisyTCP (CVE-2026-99288) Trigger Traffic — IPv4 Fragments Plus TCP SYN Flood From One Source To A Listener (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (3 of 14)

Defanged, TLP:CLEAR.

- URL: `hxxps://github[.]com/V4bel/NoisyTCP`
- File hash: `079096f103faca2dd87342cca6f23d4b34da8871`
- File hash: `4e2b3ef19e0e04adca38442f07dd6bc93c712bf1`

Full set of 14 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [NoisyTCP: 11-Year-Old Linux Kernel Flaw Lets Unauthenticated Attackers Crash Servers Remotely](https://cybersecuritynews.com/noisytcp-linux-kernel-vulnerability/)
- [NoisyTCP: Linux Kernel TCP Pre-Auth Remote Corruption (CVE-2026-99288) - researcher advisory](https://github.com/V4bel/NoisyTCP)
- [oss-security mailing list (NoisyTCP disclosure, 2026-11-15)](https://www.openwall.com/lists/oss-security/)
- [CVE-2026-99288 (NoisyTCP): Linux Kernel TCP Pre-Auth Remote Memory Corruption Fixed in 6.12.117, 6.18.63 and 7.3.4](https://securityonline.info/noisytcp-vulnerability-cve-2026-99288/)
- [NoisyTCP (CVE-2026-99288): Check, Mitigate, Patch the Kernel](https://computingforgeeks.com/linux-kernel-cve-2026-99288/)
- [Kernel-crashing NoisyTCP bug sat in Linux for 11 years](https://www.itnews.com.au/news/kernel-crashing-noisytcp-bug-sat-in-linux-for-11-years-630369)
- [NoisyTCP (CVE-2026-99288): Kernel Panic Your Patch Missed](https://www.fosslinux.com/164170/noisytcp-cve-2026-99288-linux-kernel-panic.htm)
- [Red Hat CVE page for CVE-2026-99288](https://access.redhat.com/security/cve/CVE-2026-99288)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6114
