ReconXWatchtower

Where this stands

First reported 11/11/2026 15:22

  1. 1Unconfirmednot observed
  2. 2Corroboratednot observed
  3. 3Confirmed now11/11/2026 15:22BSI CERT-Bund (WID)
  4. 4Exploitednot yet

Unconfirmed and Corroborated were never seen on its own: the first report we had was already stronger.

Linux kernel: NoisyTCP TCP pre-auth remote memory corruption (CVE-2026-99288), fixed in 6.12.117, 6.18.63 and 7.3.4

Linux kernel · CriticalFix available

CVE-2026-99288

Published 15/11/2026 23:53 · Updated 16/11/2026 09:48 (revision 3)

Timeline

3 events over 4 d 18 h

  1. 11/11/2026 15:22ConfirmedBSI CERT-Bund (WID)+4 d 8 h
  2. 15/11/2026 23:53Published on WatchtowerPro CISO+9 h
  3. 16/11/2026 09:45UpdatedThe researcher published two temporary mitigations: disabling SYN cookies, or a single…

In short

A remote attacker who can reach a vulnerable Linux server over TCP, without logging in, can exploit a race in the kernel's TCP connection lookup (named NoisyTCP by the researcher). It was first described as a kernel crash, and the researcher reports pre-authentication remote corruption. All Linux systems with the affected code are concerned. Install your distribution's kernel update (upstream 6.12.117, 6.18.63, 7.3.4) and reboot.

How bad is it

High. An attacker who can reach a vulnerable server over the network could, without logging in, crash the machine and, according to the researcher, corrupt kernel memory.

Confirmed by the vendor or a CERT - no exploitation reported yet.

Severity score

No CVSS score published yet

CVE-2026-99288: no score published yet. A missing score is never read as 0.

What an attacker needs

  • Internet access to itNot published yet
  • A loginNot published yet
  • A user to clickNot published yet
  • Special settingsNot published yet

Red helps the attacker, blue holds them back, grey is not published yet.

A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.

Affected versions

  • Linux kernels with the affected TCP established-lookup code (IPv4 and IPv6), from commit 079096f1 onward according to the CVE record.
  • Debian bookworm (6.1) and forky are listed as still vulnerable in the Debian tracker, on my reading of its columns.
  • Ubuntu 24.04 linux-hwe-7.0 is shown as 'Needs evaluation' on Ubuntu's CVE page, not as fixed.

Fixed in

  • 6.12 branch: 6.12.117
  • 6.18 branch: 6.18.63
  • 7.3 branch: 7.3.4

What to do now

  • Compare your running kernel (uname -r) with the fixed versions: upstream 6.12.117, 6.18.63, 7.3.4, and Debian trixie 6.12.117-1.
  • Install your distribution's kernel update and reboot. Hosting customers should ask their provider to do this.
  • On Ubuntu 24.04 HWE 7.0, USN-9018-2 offers 7.0.0-43.43~24.04.1, but Ubuntu has not confirmed it covers this flaw; check with Ubuntu. Ubuntu warns of an ABI change that requires recompiling third-party kernel modules.
  • If you cannot update yet, the researcher gives two temporary mitigations (oss-security, 15/11/2026). Neither replaces the update.
  • Mitigation 1 - disable SYN cookies: sysctl -w net.ipv4.tcp_syncookies=0, also in each container that has its own network namespace. This lowers the protection against SYN floods.
  • Mitigation 2 - use a single receive (RX) queue on the interface that takes outside traffic, with RPS and RFS switched off. The race needs packets to be handled on two CPUs at the same time.
  • Restricting public TCP services reduces exposure only and does not make a server safe.
  • For Debian bookworm and other branches without a listed fix, re-check the vendor trackers for a fixed version.

ReconX customers see the full notice - and their own systems

Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.

In ReconX: the full analysis, 5 open questions, followed up as sources answer, all 7 sources with their dates and every revision. And technology matching: which of your systems run Linux kernel, at which version, fixed or not - and what each one needs.

Sign in to ReconXAbout ReconX

Main sources

USN-9018-2: Linux kernel (HWE) vulnerabilities Vendor · [NEU] [hoch] Linux Kernel: Mehrere Schwachstellen CERT · NoisyTCP: Linux Kernel TCP Pre-auth Remote Corruption (CVE-2026-99288) Research

← All Watchtower notices

Pro CISO publishes ReconX Watchtower notices from public sources so organisations can act early. A notice describes an issue, never any organisation's systems. Times are Amsterdam time. Report a vulnerability in our systems.

ReconX Watchtower opened to the public on 24 October 2026, in the wake of PHP2Shell - our contribution to a safer digital ecosystem.