Rust advisories / maligned
Unsound MediumRUSTSEC-2023-0017 · maligned
RUSTSEC-2023-0017: `maligned::align_first` causes incorrect deallocation
Short answermaligned has an API that can cause undefined behaviour from safe code: `maligned::align_first` causes incorrect deallocation. No fixed version yet.
| Crate | maligned |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Medium (GitHub rating) |
| Published | 2023-03-04 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-wm8x-php5-hvq6 |
| Affected functions | maligned::align_first, maligned::align_first_boxed, maligned::align_first_boxed_cloned, maligned::align_first_boxed_default |
What to do
- Find who pulls it in:
cargo tree -i maligned. - Avoid the affected API (
maligned::align_first,maligned::align_first_boxed,maligned::align_first_boxed_cloned,maligned::align_first_boxed_default), or replace the crate.
Details from the advisory
maligned::align_first manually allocates with an alignment larger than T, and then uses Vec::from_raw_parts on that allocation to get a Vec<T>.
GlobalAlloc::dealloc requires that the layout argument must be the same layout that was used to allocate that block of memory.
When deallocating, Box and Vec may not respect the specified alignment and can cause undefined behavior.
References
- Package: crates.io/crates/maligned
- Advisory: rustsec.org/advisories/RUSTSEC-2023-0017.html
- Report: github.com/tylerhawkes/maligned/issues/5
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?