A remote sender can trigger a kernel panic before authenticating to a reachable TCP service. The Linux CVE record describes a laboratory crash, while the researcher's advisory explains the traffic and receive queue conditions.This is a host availability risk, including when the listening service runs inside a container. The researcher's advisory also describes a harder use-after-free path, but does not establish remote code execution. Administrators should identify exposed Linux hosts and verify that their deployed kernel includes the relevant fix.
What it allows
How Does CVE-2026-99288 Cause a Kernel Panic?
The Linux CVE record says TCP established socket lookup can retain an address after its original socket is freed. Another receive context can reuse that address for a new, unhashed request socket with the same connection tuple. The lookup's repeated tuple check can then accept the new object without checking whether it is hashed.
In the reproduced SYN cookie path, that new request socket has no listener attached. The TCP receive path dereferences the missing listener and panics, interrupting the Linux host. The researcher says a separate, more complex race can produce a use-after-free, but the advisory presents remote denial of service as the demonstrated outcome.
The researcher says triggering requires concurrent receive processing across at least two RX queues, or packet steering across CPUs. Ordinary reachable TCP listeners, including web and SSH services, can therefore expose an unpatched host before authentication. In the researcher's VM tests, the race triggered in about five seconds to two minutes; one quiet bare-metal test took about 14 hours.
Those timings describe controlled tests, not a predictable time to compromise. Brandefense Blackhole counted three matching dark chat posts from 18 August through 16 November 2026; the unit is posts, not incidents. The posts do not establish active exploitation. CISA's 13 November 2026 KEV catalog did not list CVE-2026-99288.
For prioritization context, see the vulnerability intelligence platform. The DDoS glossary entry explains why weakening SYN flood defenses has a cost.
Who is affected
Which Linux Kernels Are Affected by CVE-2026-99288?
The Linux CNA lists kernel versions from 4.4 as affected until their branch-specific fixes. It marks 6.12.117, 6.18.63 and 7.3.4 as fixed within their respective stable lines, plus 7.4-rc2 in the development line. The researcher identifies upstream fix commit 4e2b3ef19e0e, dated 3 November 2026.
Those version numbers do not directly identify whether a distribution kernel is patched. Distributions can carry the fix in a build with a different release number. Compare the running kernel and the distribution's security update or changelog against the relevant fix, then verify the running build after reboot. The CVE record's git commit ranges are not suitable as a simple universal version comparison, so no automated version check is proposed here.
The researcher's exposure condition is packet reachability to a TCP listener with concurrent receive contexts. Inventory Internet-facing and other untrusted-network Linux hosts first, including container hosts. A containerized listener can still bring down its underlying host if the kernel panics. The vulnerability management guide provides a broader remediation workflow.
Timeline
-
2015-10-03
The researcher dates introduction of the affected lookup behavior to Linux commit 079096f103fa.
-
2026-11-03
The researcher dates the upstream fix, commit 4e2b3ef19e0e, to this day.
-
2026-11-10
The Linux CNA published CVE-2026-99288.
-
2026-11-15
The researcher posted the NoisyTCP advisory to oss-security; its message date is 16 November in Japan time.
What to do
-
Find exposed hosts and confirm kernel provenance
Inventory Linux hosts with TCP listeners reachable from untrusted networks. Record the running kernel build, distribution, receive queue configuration and whether RPS or RFS spreads traffic across CPUs.
-
Apply the kernel fix through your distribution
Use a vendor-supported update that includes the fix for CVE-2026-99288. Upstream identifies commit 4e2b3ef19e0e; the Linux CNA lists fixed stable builds 6.12.117, 6.18.63 and 7.3.4, plus 7.4-rc2.
-
Verify the running patched build
After the required reboot, confirm the running kernel build on each host. Match it to the distribution's security notice or changelog showing the fix, including any backport, rather than relying only on a package-install record.
-
Use temporary mitigations with the tradeoff understood
If patching is delayed, the researcher suggests one RX queue with RPS and RFS disabled, or disabling SYN cookies in each relevant network namespace. Test service impact first. Disabling SYN cookies reduces SYN flood protection and is not a substitute for the fix.
-
Check for host-level failure
Review kernel panic and reboot records on exposed hosts under local incident procedures. The CNA's laboratory crash involved a NULL listener dereference; such a record warrants investigation but does not by itself attribute an attack.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-99288 in Brandefense Atlas
The Atlas record of CVE-2026-99288: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can NoisyTCP be triggered before login?
Yes. The researcher says reachable ordinary TCP listeners can expose an unpatched Linux host before authentication when receive processing races across contexts.
Does CVE-2026-99288 mean remote code execution?
The documented laboratory result is a kernel panic and remote denial of service. The researcher describes a harder use-after-free path but does not demonstrate remote code execution.
Which kernel release contains the fix?
The Linux CNA lists 6.12.117, 6.18.63 and 7.3.4 as fixed in their stable lines, plus 7.4-rc2. Verify your distribution's backported fix and running build.
Should SYN cookies be disabled as the main response?
The researcher presents that as a temporary mitigation for one path. It lowers SYN flood protection, so apply the kernel fix and verify the running build.
Sources
- NoisyTCP: Linux Kernel TCP Pre-auth Remote CorruptionHyunwoo Kim, oss-security
- CVE-2026-99288 recordLinux CNA via CVE Program
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency