NoisyTCP: Linux Kernel TCP Pre-Auth Remote Corruption (CVE-2026-99288)
Comments on “NoisyTCP: Linux Kernel TCP Pre-Auth Remote Corruption (CVE-2026-99288)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Hyunwoo Kim published an advisory for NoisyTCP (CVE-2026-99288), a Linux kernel TCP race that he says can be triggered pre-auth against default Nginx, Apache and SSH listeners on hosts with two or more RX queues or RPS. It causes a remote kernel panic; a use-after-free is possible but took seconds to minutes on VMs and about 14 hours on a quiet bare-metal server. No general exploit exists. The bug dates to 2015. Mitigations are the patch, disabling SYN cookies, or one RX queue. The advisory's figures are unverified.
Why it ranked
No. 1 of 60 with a score of 0.79. The panel rated it highest on new information (0.95) and technical depth (0.86), lowest on substantiated (0.71).
- AI judgeJudge 2claude-haiku-5-5
- Major remote kernel TCP vulnerability affecting nearly all Linux servers, with a clear technical description, mitigations, and practical impact for builders. Limited reproduction detail and a stated lab-only exploit temper substantiation.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed advisory for a pre-auth, remotely triggerable Linux TCP race causing kernel-wide DoS, with affected versions, trigger conditions, exploitability, patch, and mitigations. It is highly actionable and broadly relevant to Linux operators.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.79total under rubric v2.3
- Significance0.78
- Reader interest0.84
- Audience breadth0.84
- Practical relevance0.84
- Substantiated0.71
- Technical depth0.86
- New information0.95
- Counts against: Promotional0.03
- Counts against: Overclaim0.28
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.72 | 0.80 | 0.82 | 0.78 | 0.10 | +0.24 | +0.188 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.70 | 0.93 | 0.90 | 0.84 | 0.23 | +0.26 | +0.219 |
| Audience breadthHow many people who build technology does it concern? | 0.80 | 0.85 | 0.88 | 0.84 | 0.08 | +0.13 | +0.110 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.76 | 0.85 | 0.90 | 0.84 | 0.14 | +0.22 | +0.184 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.57 | 0.70 | 0.86 | 0.71 | 0.29 | +0.05 | +0.036 |
| Technical depthHow technically substantive is it? | 0.91 | 0.80 | 0.88 | 0.86 | 0.10 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.95 | 1.00 | 0.95 | 0.10 | +0.05 | +0.048 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.03 | 0.01 | 0.03 | 0.05 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.43 | 0.30 | 0.12 | 0.28 | 0.31 | −0.11 | −0.031 |
| Sum of contributions | +0.789 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.789 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-16/1/"><img src="https://rubric.hrih.si/badge/2026-11-16/1.svg" alt="Ranked #1 on Rubric, 16 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkNumber
NoisyTCP (CVE-2026-99288) was reported and patched by Hyunwoo Kim (@v4bel).
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “reported and patched by Hyunwoo Kim (@v4bel”
The source says No passage could be compared.
Source cited by the article: x.com/v4bel
No source givenNumber
Against Nginx, Apache and SSH servers with default configuration on VMs such as QEMU/KVM, triggering the vulnerability took about 5 seconds to 2 minutes.
The article gives no link or citation for it.
The article says “it took about 5 seconds to 2 minutes to trigger”
The source says No source to compare with.
No source givenNumber
Against Nginx with default configuration on a quiet bare-metal server with 8 RX queues, triggering took about 14 hours even with a PoC tuned for the environment.
The article gives no link or citation for it.
The article says “it took about 14 hours to trigger, even though a PoC with race timing carefully tuned for the target environment was used”
The source says No source to compare with.
No source givenDate
The vulnerability was introduced in commit 079096f103fa (2015-10-03) and fixed in commit 4e2b3ef19e0e (2026-11-03).
The article gives no link or citation for it.
The article says “Introduced: 079096f103fa (2015-10-03) - Fixed: 4e2b3ef19e0e (2026-11-03”
The source says No source to compare with.
No source givenGeneralization
The vulnerability had been latent in the Linux kernel for about 11 years and affects almost all Linux distributions.
The article gives no link or citation for it.
The article says “this vulnerability had been latent in the Linux kernel for about "11 years" and affects almost all Linux distributions”
The source says No source to compare with.
No source givenCausal conclusion
The vulnerability can be triggered pre-auth and remotely against plain TCP listeners such as default-configured Nginx, Apache and SSH servers.
The article gives no link or citation for it.
The article says “it can be triggered pre-auth and remotely against servers that TCP packets sent by an attacker can reach directly, such as Nginx, Apache, and SSH servers”
The source says No source to compare with.
No source givenNumber
The default value of net.ipv4.tcp_syncookies is 1 on most Linux distributions, and setting it to 0 blocks the SYN cookie request socket reconstruction path.
The article gives no link or citation for it.
The article says “The default value of this setting is 1 on most Linux distributions”
The source says No source to compare with.
No source givenCausal conclusion
A DoS triggered against a web server in a container takes down the entire host, because it is a kernel vulnerability.
The article gives no link or citation for it.
The article says “it takes down not only the web server application but the entire host”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 8 pts, not on front page
Recorded for context only, checked 16 Nov 2026, 05:47 UTC. It played no part in the ranking.