GHSA-fg7r-2g4j-5cgr

Suggest an improvement
Source
https://github.com/advisories/GHSA-fg7r-2g4j-5cgr
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-fg7r-2g4j-5cgr/GHSA-fg7r-2g4j-5cgr.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-fg7r-2g4j-5cgr
Aliases
Published
2022-01-06T22:04:37Z
Modified
2023-11-01T04:56:55.327411Z
Severity
  • 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
Race Condition in tokio
Details

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

Affected packages

crates.io / tokio

Package

Affected ranges

Type
SEMVER
Events
Introduced
0.1.14
Fixed
1.8.4

Ecosystem specific

{
    "affected_functions": [
        "tokio::sync::oneshot::Receiver::close"
    ]
}

crates.io / tokio

Package

Affected ranges

Type
SEMVER
Events
Introduced
1.9.0
Fixed
1.13.1

Ecosystem specific

{
    "affected_functions": [
        "tokio::sync::oneshot::Receiver::close"
    ]
}