Advisory

RUSTSEC-2026-0282

Also known as: None

Summary

Double free in AlignedBox<[T]>::realloc_with_default when an element's Drop panics

Details

Shrinking an AlignedBox<[T]> takes ownership of the buffer out of
self.container with ManuallyDrop::take, destroys the elements past the new
length, and only then commits the new Box back into self.container.
ManuallyDrop::take moves ownership but not the bits, so until that commit
self.container still points at the original buffer.

T::drop runs inside the destruction loop and is user code — T carries no
bound that would exclude a panicking Drop. If it unwinds, the commit is
skipped and self.container is left pointing at the buffer whose tail has
already been destroyed. AlignedBox's own destructor then reconstructs a Box
from that pointer, drops every element again and deallocates — a double free
(CWE-415) / use-after-free (CWE-416) reachable from safe Rust.

Growing the slice destroys nothing and is unaffected, as is
realloc_with_value, which requires T: Copy and therefore a Drop that
cannot run.

Mitigation

Update to 0.3.1.

Severity

Not rated by the source.

Dates

Published
2026-09-09 12:00 UTC
Modified
2026-09-09 11:00 UTC

Affected packages and fixes

aligned_box

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.3.1 (semver)

Fixed versions

0.3.1

Fix

  • Fixed version 0.3.1
    cargo update -p aligned_box --precise 0.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences