Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 23 Oct 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Tokio: Race condition in `tokio::time::Interval` | |
| Weaknesses | CWE-362 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-23T17:13:16.161Z
Reserved: 2026-10-22T22:53:15.237Z
Link: CVE-2026-115567
No data.
Status : Awaiting Analysis
Published: 2026-10-23T18:17:21.303
Modified: 2026-10-23T19:42:24.553
Link: CVE-2026-115567
No data.
OpenCVE Enrichment
Updated: 2026-10-23T19:30:18Z
-
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')