Skip to content
Fencer Intel
low —

GHSA-rr8g-9fpq-6wmg json

Tokio broadcast channel calls clone in parallel, but does not require `Sync`

published last yr. modified 2mo ago also RUSTSEC-2025-0023

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The broadcast channel internally calls `clone` on the stored value when receiving it, and only requires `T:Send`. This means that using the broadcast channel with values that are `Send` but not `Sync` can trigger unsoundness if the `clone` implementation makes use of the value being `!Sync`.

Thank you to Austin Bonander for finding and reporting this issue.

Patch / fix

  • crates.io tokio 1.38.2, 1.42.1, 1.43.1, 1.44.2

Is GHSA-rr8g-9fpq-6wmg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io tokio
>=1.44.0, <1.44.2
>=0.2.5, <1.38.2
>=1.39.0, <1.43.1
>=1.39.0, <1.42.1
>=1.43.0, <1.43.1
1.44.2
1.38.2
1.43.1
1.42.1

Classification

Weakness
  • CWE-664 Improper Control of a Resource Through its Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.