Description
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.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | tokio | >= 1.44.0, < 1.44.2 | 1.44.2 | GHSA-rr8g-9fpq-6wmg |
| crates.io | tokio | >= 0.2.5, < 1.38.2 | 1.38.2 | GHSA-rr8g-9fpq-6wmg |
| crates.io | tokio | >= 1.39.0, < 1.43.1 | 1.43.1 | GHSA-rr8g-9fpq-6wmg |
| crates.io | tokio | >= 0.2.5, < 1.38.2 · >= 1.39.0, < 1.42.1 · >= 1.43.0, < 1.43.1 · >= 1.44.0, < 1.44.2 | 1.38.2, 1.42.1, 1.43.1, 1.44.2 | RUSTSEC-2025-0023 |