Rust advisories / crossbeam-channel
Vulnerability MediumRUSTSEC-2025-0024 · crossbeam-channel
RUSTSEC-2025-0024: crossbeam-channel: double free on Drop
Short answerA security vulnerability in the crossbeam-channel crate: crossbeam-channel: double free on Drop. GitHub rates it Medium. Fixed in 0.5.15: update to a fixed version.
| Crate | crossbeam-channel |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | From 0.5.12 before 0.5.15. |
| Fixed in | 0.5.15 |
| Severity | Medium (GitHub rating) |
| Published | 2025-04-08 |
| Last changed | 2025-10-28 |
| Also known as | CVE-2025-4574, GHSA-pg9f-39pc-qf8g, TROVE-2025-013 |
What to do
- See which version you have:
cargo tree -i crossbeam-channel(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p crossbeam-channel. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplecrossbeam-channel = "0.5.15") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The internal Channel type's Drop method has a race which could, in some circumstances, lead to a double-free. This could result in memory corruption.
Quoting from the upstream description in merge request \#1187:
> The problem lies in the fact that dicard_all_messages contained two paths that could lead to head.block being read but only one of them would swap the value. This meant that dicard_all_messages could end up observing a non-null block pointer (and therefore attempting to free it) without setting head.block to null. This would then lead to Channel::drop making a second attempt at dropping the same pointer.
The bug was introduced while fixing a memory leak, in upstream MR \#1084, first published in 0.5.12.
The fix is in upstream MR \#1187 and has been published in 0.5.15
References
- Package: crates.io/crates/crossbeam-channel
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0024.html
- Web: github.com/crossbeam-rs/crossbeam/pull/1187
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for crossbeam-channel
Up next
Same cratecrossbeam-channel: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?