RUSTSEC-2026-0384: Race condition in `tokio::time::Interval` on Tokio v1.54.0

Aberta
  • Algo errado?
#326 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
20/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Race condition in tokio::time::Interval on 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.

Linguagem predominante
Rust
Estrelas
2
Forks
2
Merge médio
13h 13min
PRs com merge (30d)
5

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DiamondLightSource/numtracker

Todas as issues de DiamondLightSource/numtracker

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.