NoisyTCP
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 disclosed NoisyTCP (CVE-2026-99288), a Linux TCP race present since a 2015 commit and fixed on 2026-11-03. It needs packets handled on separate RX queues or CPUs. The easier path ends in a NULL listener dereference and a remote kernel panic; a use-after-free path is described as much harder. Kim reports 5 seconds to 2 minutes on VMs but about 14 hours on a quiet 8-queue bare-metal host. These figures are his own. Mitigations: disable SYN cookies per network namespace, or use a single RX queue.
Why it ranked
No. 3 of 122 with a score of 0.78. The panel rated it highest on practical relevance (0.88) and reader interest (0.87), lowest on new information (0.50). The judges disagreed most on new information (spread 0.84), so the story is marked contested. Placed No. 3, where the score alone would also have put it: close to “NoisyTCP: Linux Kernel TCP Pre-Auth Remote Corruption (CVE-2026-99288)”, No. 1 on Monday 16 November 2026 (−0.008). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Major disclosed Linux kernel TCP remote pre-auth vulnerability with detailed trigger flows and mitigations; highly relevant to security and infrastructure builders. Primary advisory text, but reproduction claims are partly unverified; new relative to the listed stories.
- AI judgeJudge 3gpt-5.6-luna
- A primary, technically detailed disclosure of a long-lived, remotely triggerable Linux TCP race affecting common servers, with reproduction characteristics and concrete mitigations. It duplicates a listed recent story, while “corruption” slightly exceeds the demonstrated impact.
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.78total under rubric v2.3Contestedjudges differ by 0.84 on new information
- Significance0.79
- Reader interest0.87
- Audience breadth0.86
- Practical relevance0.88
- Substantiated0.73
- Technical depth0.86
- New information0.50
- Counts against: Promotional0.04
- Counts against: Overclaim0.39
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.86 | 0.79 | 0.14 | +0.24 | +0.191 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.75 | 0.93 | 0.94 | 0.87 | 0.19 | +0.26 | +0.227 |
| Audience breadthHow many people who build technology does it concern? | 0.79 | 0.90 | 0.88 | 0.86 | 0.11 | +0.13 | +0.112 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.80 | 0.90 | 0.93 | 0.88 | 0.13 | +0.22 | +0.193 |
| 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.66 | 0.60 | 0.94 | 0.73 | 0.34 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.90 | 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.65 | 0.85 | 0.01 | 0.50 | 0.84 , above the contested threshold | +0.05 | +0.025 |
| 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.08 | 0.03 | 0.01 | 0.04 | 0.07 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.38 | 0.30 | 0.48 | 0.39 | 0.18 | −0.11 | −0.043 |
| Sum of contributions | +0.776 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.776 | ||||||
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-17/3/"><img src="https://rubric.hrih.si/badge/2026-11-17/3.svg" alt="Ranked #3 on Rubric, 17 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenVersion
NoisyTCP (CVE-2026-99288) was introduced in Linux kernel commit 079096f103fa dated 2015-10-03 and fixed in commit 4e2b3ef19e0e dated 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 givenNumber
The NoisyTCP 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 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 target 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 givenCausal conclusion
The request_sock reuse ABA race leads the TCP receive path to dereference a NULL listener, causing a kernel panic and a remote DoS.
The article gives no link or citation for it.
The article says “the TCP receive path dereferences the NULL listener, which causes a kernel panic”
The source says No source to compare with.
No source givenGeneralization
Because the vulnerability can be triggered against plain TCP listeners, it can be exploited pre-auth and remotely against default-configured servers such as Nginx, Apache, and SSH.
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 running with their "default"…”
The source says No source to compare with.
No source givenCausal conclusion
A DoS against a web server running in a container takes down the entire host, not just the web server application, because it is a Linux kernel TCP vulnerability.
The article gives no link or citation for it.
The article says “if the DoS is triggered against a web server running in a container, it takes down not only the web server application but the entire host”
The source says No source to compare with.
No source givenGeneralization
The vulnerability can be triggered against servers with two or more RX queues, or where RPS distributes packets across multiple CPUs.
The article gives no link or citation for it.
The article says “it can be triggered against servers that have two or more RX queues, or where RPS distributes packets across multiple CPUs”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.