Vulnerability Description
Tokio is a runtime for writing applications with Rust. In 1.54.0, a race condition between tokio::time::Interval::poll_tick (including .tick().await) and the multi-threaded runtime's time driver could drop an internal timer entry without synchronizing with the driver thread that was firing it. The race caused a use-after-free on the timer's waker and task state in safe Rust, which could produce assertion panics, task reference-count corruption, or heap memory corruption. This issue is fixed in 1.54.1.
Related Weaknesses (CWE)
References
- https://github.com/tokio-rs/tokio/commit/2b4eba7833864c04ecd2f3e5f4a97ff4f6fa28d
- https://github.com/tokio-rs/tokio/commit/5ed619bbaba87357ee5103d71b75e7c84cad99c
- https://github.com/tokio-rs/tokio/pull/8458
- https://github.com/tokio-rs/tokio/pull/8692
- https://github.com/tokio-rs/tokio/releases/tag/tokio-1.54.1
- https://github.com/tokio-rs/tokio/security/advisories/GHSA-5wjr-9356-4wc8
FAQ
What is CVE-2026-115567?
CVE-2026-115567 is a documented vulnerability. Tokio is a runtime for writing applications with Rust. In 1.54.0, a race condition between tokio::time::Interval::poll_tick (including .tick().await) and the multi-threaded runtime's time driver could...
How severe is CVE-2026-115567?
CVSS scoring is not yet available for CVE-2026-115567. Check NVD for updates.
Is there a patch for CVE-2026-115567?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.