Rust advisories / crossbeam-queue
Unsound MediumRUSTSEC-2022-0021 · crossbeam-queue
RUSTSEC-2022-0021: `SegQueue` creates zero value of any type
Short answercrossbeam-queue has an API that can cause undefined behaviour from safe code: `SegQueue` creates zero value of any type. Fixed in 0.2.3.
| Crate | crossbeam-queue |
|---|---|
| Type | Unsound |
| Affected versions | Before 0.2.3. |
| Fixed in | 0.2.3 |
| Severity | Medium (GitHub rating) |
| Published | 2022-05-10 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-6888-wf7j-34jq |
What to do
- See which version you have:
cargo tree -i crossbeam-queue(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p crossbeam-queue. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplecrossbeam-queue = "0.2.3") 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
Affected versions of this crate called mem::zeroed() to create values of a user-supplied type T. This is unsound e.g. if T is a reference type (which must be non-null).
The flaw was corrected by avoiding the use of mem::zeroed(), using MaybeUninit instead.
References
- Package: crates.io/crates/crossbeam-queue
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0021.html
- Web: github.com/crossbeam-rs/crossbeam/pull/458
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratecrossbeam-queue: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?