The Linux TCP flaw is worse than we thought
Comments on “The Linux TCP flaw is worse than we thought”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A Firezone blog post warns that a Linux kernel use-after-free bug, CVE-2026-98432, affects TCP connections in kernels back to 4.4 and can be triggered by SYN packets carrying IP options.
Why it ranked
No. 56 of 143 with a score of 0.65. The panel rated it highest on technical depth (0.93) and practical relevance (0.90), lowest on new information (0.64). The judges disagreed most on new information (spread 0.73), so the story is marked contested. The claim check took 0.100 off. Placed No. 56, No. 40 by score alone: the 16th Security story of the day (−0.080), and close to “Well, That Wasn't Fun: October 16 '26”, No. 22 on Saturday 7 November 2026 (−0.009). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, practical analysis of a serious Linux kernel use-after-free flaw with mitigations and the real fix; substantive and actionable, though the vendor-promotional closing and the coverage overlap with the same CVE in the recent list reduce novelty and score.
- AI judgeJudge 3gpt-5.6-luna
- Detailed technical analysis of a serious Linux TCP use-after-free, including trigger conditions, incomplete mitigations, kernel patch mechanics, and actionable XDP/nftables guidance. The closing service pitch is minor relative to the substantive security content.
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.65total under rubric v2.3Contestedjudges differ by 0.73 on new information
- Significance0.74
- Reader interest0.84
- Audience breadth0.76
- Practical relevance0.90
- Substantiated0.80
- Technical depth0.93
- New information0.64
- Counts against: Promotional0.16
- Counts against: Overclaim0.27
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.71 | 0.72 | 0.78 | 0.74 | 0.07 | +0.24 | +0.177 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.79 | 0.85 | 0.88 | 0.84 | 0.09 | +0.26 | +0.218 |
| Audience breadthHow many people who build technology does it concern? | 0.77 | 0.80 | 0.72 | 0.76 | 0.08 | +0.13 | +0.099 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.90 | 0.90 | 0.91 | 0.90 | 0.01 | +0.22 | +0.199 |
| 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.74 | 0.80 | 0.86 | 0.80 | 0.12 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.90 | 0.93 | 0.10 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.78 | 0.20 | 0.93 | 0.64 | 0.73 , above the contested threshold | +0.05 | +0.032 |
| 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.09 | 0.20 | 0.18 | 0.16 | 0.11 | −0.19 | −0.030 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.42 | 0.20 | 0.20 | 0.27 | 0.22 | −0.11 | −0.030 |
| Sum of contributions | +0.752 | ||||||
| Claim-check penalty | −0.100 | ||||||
| Total, as published | 0.652 | ||||||
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-11/56/"><img src="https://rubric.hrih.si/badge/2026-11-11/56.svg" alt="Ranked #56 on Rubric, 11 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 matches source · 1 not in source · 2 no source given · 3 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 checkVersion
CVE-2026-98432 is a use-after-free vulnerability affecting Linux kernels going back to version 4.4.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “the use-after-free vulnerability in Linux kernels going back to 4.4 (10+ years ago”
The source says No passage could be compared.
Source cited by the article: nvd.nist.gov/vuln/detail/cve-2026-98432
Matches sourceCausal conclusion
Anthropic's original discovery of the vulnerability used a Multipath TCP listener as its way in.
The cited source says the same thing.
The article says “The original discovery by Anthropic used a Multipath TCP listener as its way in”
The source says “Claude wrote an exploit that allows a remote attacker to send packets to Linux servers with a multipath TCP listener to run arbitrary commands as root”
Source cited by the article: anthropic.com/research/discovering-vulnerabilities-with-claude
Matches sourceQuote
The Go team described disabling MPTCP as a "fragile mitigation" and said the real fix is to upgrade to a patched kernel.
The cited source says the same thing.
The article says “noting this is however a "fragile mitigation" and the real fix is to upgrade to a patched kernel”
The source says “Note that disabling MPTCP on a program-by-program basis is a fragile mitigation”
Source cited by the article: openwall.com/lists/oss-security/2026/10/30/1
No source givenVersion
Go 1.24 and later enable MPTCP on Linux TCP listeners by default.
The article gives no link or citation for it.
The article says “Golang >= 1.24 enables MPTCP on Linux TCP listeners by default”
The source says No source to compare with.
Not in sourceVersion
As of Gateway 1.6.5, Linux GUI Client 1.5.21, and Linux Headless Client 1.5.16, Firezone strips options from IPv4 packets in both directions.
The cited source does not contain it.
The article says “as of Gateway 1.6.5, Linux GUI Client 1.5.21, and Linux Headless Client 1.5.16, Firezone strips options from IPv4 packets in both directions”
The source says “15736 Greatly improves tunnel throughput by parallelizing WireGuard encryption and decryption across worker threads”
Source cited by the article: firezone.dev/changelog
Couldn’t checkNumber
The fix commit e3f33b0a1d89 changes two kfree() calls to kfree_rcu(), so IP options are only freed after every CPU still reading them has finished.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “changes two kfree() calls to kfree_rcu(), so the options are only freed once every CPU still reading them has finished”
The source says No passage could be compared.
Source cited by the article: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit
Couldn’t checkVersion
The fix first shipped in Linux 7.3 and is being backported to stable kernels.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “It first shipped in Linux 7.3 and is being backported to stable kernels”
The source says No passage could be compared.
Source cited by the article: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit
No source givenGeneralization
Because the fix changes how memory is freed rather than how options get there, it closes every problematic code path, including the gaps left by dropping packets with options.
The article gives no link or citation for it.
The article says “it closes every problematic code path above, including the gaps”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 4 pts, not on front page
Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.