tokio
Affected
- introduced
0.1.14, fixed1.8.4, introduced1.9.0, fixed1.13.1(semver)
Fixed versions
1.8.4, 1.13.1
Fix
- Fixed version
1.8.4cargo update -p tokio --precise 1.8.4 - Fixed version
1.13.1cargo update -p tokio --precise 1.13.1
Advisory
Also known as: CVE-2021-45710, GHSA-fg7r-2g4j-5cgr
Data race when sending and receiving after closing a oneshot channel
If a tokio::sync::oneshot channel is closed (via the
[oneshot::Receiver::close] method), a data race may occur if theoneshot::Sender::send method is called while the correspondingoneshot::Receiver is awaited or calling try_recv.
When these methods are called concurrently on a closed channel, the two halves
of the channel can concurrently access a shared memory location, resulting in a
data race. This has been observed to [cause memory corruption][corruption].
Note that the race only occurs when both halves of the channel are used
after the Receiver half has called close. Code where close is not used, or where theReceiver is not awaited and try_recv is not called after calling close,
is not affected.
See [tokio#4225][issue] for more details.
[corruption]: https://github.com/tokio-rs/tokio/issues/4225#issuecomment-967434847
[issue]: https://github.com/tokio-rs/tokio/issues/4225
[oneshot::Receiver::close]: https://docs.rs/tokio/1.14.0/tokio/sync/oneshot/struct.Receiver.html#method.close
Not rated by the source.
0.1.14, fixed 1.8.4, introduced 1.9.0, fixed 1.13.1 (semver)1.8.4, 1.13.1
1.8.4cargo update -p tokio --precise 1.8.41.13.1cargo update -p tokio --precise 1.13.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0