Race Condition in tokio
High severity
GitHub Reviewed
Published
Jan 6, 2022
to the GitHub Advisory Database
•
Updated Jun 13, 2023
Package
Affected versions
>= 1.9.0, < 1.13.1
>= 0.1.14, < 1.8.4
Patched versions
1.13.1
1.8.4
Description
Published by the National Vulnerability Database
Dec 27, 2021
Reviewed
Jan 5, 2022
Published to the GitHub Advisory Database
Jan 6, 2022
Last updated
Jun 13, 2023
If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::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.
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 the Receiver is not awaited and try_recv is not called after calling close, is not affected.
References