Edition of Wednesday 18 November 2026

Taking Time Out of Toctou: From Race Reproduction to Security Discovery

Comments on “Taking Time Out of Toctou: From Race Reproduction to Security Discovery”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Researchers at the University of Calgary describe Chronos, a Linux framework that holds a program at the "use" syscall, via seccomp notifications, until a declared attacker change completes, so one trial can label a build vulnerable, fixed or indeterminate. In the authors' evaluation, effect-only checkers made over 800 false-fixed calls where Chronos made none, and all 27 bisections found the expected commits. It also flagged incomplete fixes in chrony and rpm. These results are the authors' own, and two kernel cases remain one-sided.

Read the original at arxiv.org. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 17 of 142 with a score of 0.72. The panel rated it highest on technical depth (0.96) and new information (0.94), lowest on audience breadth (0.60). Placed No. 17, No. 7 by score alone: the sixth Security story of the day (−0.060). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Rigorous research on reproducing TOCTOU races in container runtimes, with a reusable one-trial oracle, bisection evaluation and real incomplete-fix findings; strong technical depth and substantiation, but niche audience.
AI judgeJudge 3gpt-5.6-luna
A deeply technical research paper presents Chronos, a reproducible single-trial oracle for TOCTOU security races, with formal assumptions, implementation details, extensive evaluations, bisection results, and discovered incomplete fixes.

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.72total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.66
  • Reader interest0.82
  • Audience breadth0.60
  • Practical relevance0.74
  • Substantiated0.90
  • Technical depth0.96
  • New information0.94
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.24

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.620.550.820.660.27+0.24+0.159
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.660.850.940.820.28+0.26+0.212
Audience breadthHow many people who build technology does it concern?0.580.600.620.600.04+0.13+0.078
Practical relevanceHow useful is it to someone who builds software or tech products?0.680.700.860.740.18+0.22+0.164
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.980.800.910.900.18+0.05+0.045
Technical depthHow technically substantive is it?0.980.900.990.960.09+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.950.980.940.08+0.05+0.047
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.060.050.010.040.05−0.19−0.008
OverclaimDo the headline or conclusions claim more than the body supports?0.290.250.180.240.11−0.11−0.026
Sum of contributions+0.719
Claim-check penalty0.000
Total, as published0.719

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.

Ranked #17 on Rubric, 18 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-18/17/"><img src="https://rubric.hrih.si/badge/2026-11-18/17.svg" alt="Ranked #17 on Rubric, 18 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 1 matches source · 6 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.

  1. No source givenNumber

    For CVE-2021-30465, the attack succeeded in all 100 runs of the vulnerable runc version with Chronos and in 603 of 2,000 runs without it.

    The article gives no link or citation for it.

    The article says

    “the attack succeeded in all 100 runs of the vulnerable version with Chronos and in 603 of 2,000 runs without it”

    The source says

    No source to compare with.

  2. No source givenNumber

    On known-vulnerable builds, effect-only checkers made over 800 false-fixed classifications in failed-intervention trials, while Chronos made none.

    The article gives no link or citation for it.

    The article says

    “effect-only checkers made over 800 false-fixed classifications in failed-intervention trials; Chronos made none”

    The source says

    No source to compare with.

  3. No source givenNumber

    All 27 historical bisections recovered the expected boundary commits.

    The article gives no link or citation for it.

    The article says

    “All 27 historical bisections recovered the expected boundaries”

    The source says

    No source to compare with.

  4. No source givenBenchmark result

    For runc's CVE-2025-31133 bisection with one victim per launch, fixed retry and Git Bayesect took medians of 475 and 398 natural launches, while Chronos used seven held trials.

    The article gives no link or citation for it.

    The article says

    “fixed retry and Git Bayesect took medians of 475 and 398 natural launches; Chronos used seven held trials including endpoint checks”

    The source says

    No source to compare with.

  5. Matches sourceNumber

    In the CVE-2021-30465 discoverer's demonstration, 6 of 19 victim containers escaped when raced against four swap loops.

    The cited source says the same thing.

    The article says

    “To demonstrate CVE-2021-30465, its discoverer raced 19 victim containers against four swap loops, after a smaller setup always failed; 6 of the 19 escaped”

    The source says

    “I then switched to a C version (not sure it makes a difference), 19 containers and 4 mounts and this worked and gave me 6 containers out of 19 with…”

    Source cited by the article: github.com/champtar/blog/blob/main/runc-symlink-CVE-2021-30465/README.md

  6. No source givenNumber

    Races caused 12 of 20 sampled reproduction failures in syzbot's cause bisection.

    The article gives no link or citation for it.

    The article says

    “races caused 12 of 20 sampled reproduction failures in syzbot’s cause bisection”

    The source says

    No source to compare with.

  7. No source givenFirst, only or fastest

    Chronos helped uncover three issues: incomplete fixes in chrony and rpm, and a Debian 12 rpm package that Debian's tracker listed as fixed but was labeled vulnerable.

    The article gives no link or citation for it.

    The article says

    “Chronos helped us uncover three issues: incomplete fixes in chrony and rpm, and a Debian rpm package its tracker listed as fixed”

    The source says

    No source to compare with.

  8. Couldn’t checkNumber

    17 of the 41 zero-days exploited in the wild in 2022 were variants of previously reported vulnerabilities.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “17 of the 41 zero-days exploited in the wild in 2022 were variants of previously reported vulnerabilities”

    The source says

    No passage could be compared.

    Source cited by the article: security.googleblog.com/2023/07/the-ups-and-downs-of-0-days-year-in.html

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 18 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Taking Time Out of Toctou: From Race Reproduction to Security Discovery”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.