RUSTSEC-2026-0384: Race condition in `tokio::time::Interval` on Tokio v1.54.0
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 20/100
Línea de trabajo
The issue reports a Tokio vulnerability and links to its fix at tokio-rs/tokio#8692, but it does not identify a change needed in numtracker. First check the project's Tokio dependency and whether it can use a patched version (>=1.54.1); done means numtracker no longer depends on the affected 1.54.0 release.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Race condition in
tokio::time::Intervalon Tokio v1.54.0
| Details | |
|---|---|
| Package | tokio |
| Version | 1.54.0 |
| URL | https://github.com/tokio-rs/tokio/pull/8692 |
| Date | 2026-10-21 |
| Patched versions | >=1.54.1 |
| Unaffected versions | <1.54.0 |
Summary
On the multi-threaded runtime, there is a race condition between Interval::poll_tick and the runtime's time driver.
This affects Interval only. Sleep and Timeout are not affected.
Details
In Tokio v1.54.0, a race condition between tokio::time::Interval::poll_tick (including .tick().await) and the runtime time driver can drop an internal timer entry without synchronizing with the driver thread that is firing it. This causes a data race and use-after-free on the timer's waker and task state in safe Rust, leading to assertion panics, task reference-count corruption, or heap memory corruption.
This bug was introduced by https://github.com/tokio-rs/tokio/pull/8458, and it was fixed by https://github.com/tokio-rs/tokio/pull/8692.
Impact
This may lead to crashes and use-after-frees in applications using Interval on a multi-threaded runtime.
Since this issue is known to lead to crashes in production systems, the v1.54.0 release of Tokio has been yanked.
Credits
Thank you to creepycode and carabistouille for reporting this privately using the procedure outlined in our security policy. They both reported the issue independently of each other.
See advisory page for additional details.
- Lenguaje dominante
- Rust
- Estrellas
- 2
- Forks
- 2
- Merge medio
- 13 h 13 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DiamondLightSource/numtracker
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
DiamondLightSource/numtracker#309 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
DiamondLightSource/numtracker#278 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
DiamondLightSource/numtracker#329 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
DiamondLightSource/numtracker#325 ·
-
RUSTSEC-2026-0387: Multiple timing variability issues in operations intended to be constant-timeAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 1/100
DiamondLightSource/numtracker#324 ·
Todos los issues de DiamondLightSource/numtracker
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Non-`main` default branchesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
max-sixty/worktrunk#4727 · 7 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
carrick-sh/carrick#1859 ·
Los mantenedores suelen responder en 1 día
-
crate: spate-kafka documentation priority: medium
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día