# Taking Time Out of TOCTOU: From Race Reproduction to Security Discovery

DevFeed: [Taking Time Out of TOCTOU: From Race Reproduction to Security Discovery](<https://devfeed.tech/articles/taking-time-out-of-toctou-from-race-reproduction-to-security-discovery-138011.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.21214>)

Author: Hasnain Naeem, Ryan Henry

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-os](<https://devfeed.tech/tags/cs-os.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [debian](<https://devfeed.tech/tags/debian.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [indeterminate](<https://devfeed.tech/tags/indeterminate.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kvm](<https://devfeed.tech/tags/kvm.md>), [linux](<https://devfeed.tech/tags/linux.md>), [oracles](<https://devfeed.tech/tags/oracles.md>), [race](<https://devfeed.tech/tags/race.md>), [regression](<https://devfeed.tech/tags/regression.md>), [reproduction](<https://devfeed.tech/tags/reproduction.md>), [rpm](<https://devfeed.tech/tags/rpm.md>), [runc](<https://devfeed.tech/tags/runc.md>), [seccomp](<https://devfeed.tech/tags/seccomp.md>), [security](<https://devfeed.tech/tags/security.md>), [specifications](<https://devfeed.tech/tags/specifications.md>)

## AI overview

Chronos makes TOCTOU race tests more reproducible by separating timing interventions from verdict evidence. Its reusable Race Specifications combine hold engines, attack actions, observers, and outcome rules. On stock Linux, seccomp notifications enforce syscall-boundary hold-attack-release ordering; ptrace and a KVM guest gate support userspace and kernel instruction sites. A run is labeled fixed only with positive, case-specific evidence; missing or contradictory required evidence stays indeterminate. In the reported tests, effect-only checkers produced over 800 false-fixed results in failed-intervention trials, while Chronos produced none. All 27 historical bisections recovered expected boundaries. For runc's masked-path bisection, Chronos used seven held trials including endpoint checks, versus median counts of 475 natural launches for fixed retry and 398 for Git Bayesect. Two kernel cases remained one-sided. Applying the specifications to releases and packages uncovered incomplete fixes in chrony and rpm, plus a Debian rpm package listed as fixed.

## Source excerpt

arXiv:2611.21214v1 Announce Type: cross Abstract: Time-of-check-to-time-of-use (TOCTOU) races are hard to reproduce and lost races can make vulnerable programs look fixed. We present Chronos, a framework that separates intervention timing from verdict evidence and builds reusable one-trial security regression oracles from declared races for deterministic reproduction, commit bisection and CI. Race Specifications compose reusable hold engines, actions, observers and outcome rules. When the declared hold is reached and the attack completes while held, Chronos orders it before the use under blocking and interference assumptions. Chronos uses seccomp notifications to enforce declared hold-attack-release ordering at syscall boundaries on stock Linux; ptrace and a KVM guest gate provide holds at userspace and kernel instruction sites. One decision procedure labels every mechanism's runs: fixed requires positive, case-specific evidence of preservation, justified refusal, omission under checked coverage, or a declared rule; missing or contradictory required evidence remains indeterminate. On known-vulnerable builds, effect-only checkers made over 800 false-fixed classifications in failed-intervention trials; Chronos made none. All 17 syscall-held cases and four of six instruction-held cases had vulnerable and fixed labels. Two kernel cases remain one-sided. All 27 historical bisections recovered the expected boundaries. For runc's masked-path bisection with one victim per launch, fixed retry and Git Bayesect took medians of 475 and 398 natural launches; Chronos used seven held trials including endpoint checks. Since a label means the same however a fix is written, we also ran the specifications and attack variants on releases, distribution packages and other runtimes. There, Chronos helped us uncover three issues: incomplete fixes in chrony and rpm, and a Debian rpm package its tracker listed as fixed.