Rust advisories / linkme
Unsound LowRUSTSEC-2024-0407 · linkme
RUSTSEC-2024-0407: Fails to ensure slice elements match the slice's declared type
Short answerlinkme has an API that can cause undefined behaviour from safe code: Fails to ensure slice elements match the slice's declared type. Fixed in 0.3.24.
| Crate | linkme |
|---|---|
| Type | Unsound |
| Affected versions | Before 0.3.24. |
| Fixed in | 0.3.24 |
| Severity | Low (GitHub rating) |
| Published | 2024-03-05 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-f95p-4cv5-8w8x |
What to do
- See which version you have:
cargo tree -i linkme(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p linkme. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelinkme = "0.3.24") 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 allow populating a DistributedSlice of T with elements of an arbitrary other type that coerces to T. For example, elements of type &&str could end up in a slice of type [&str], since &&str coerces to &str via a deref coercion.
The flaw was corrected by implementing typechecking for distributed slice elements in such a way that coercion no longer occurs. The element's type must be a subtype of the slice's declared element type.
References
- Package: crates.io/crates/linkme
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0407.html
- Report: github.com/dtolnay/linkme/issues/82
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
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?