Reported

August 11, 2026

Issued

August 12, 2026

Package

sized-chunks (crates.io)

Type

INFO Unsound

Categories

• memory-corruption

Keywords

#panic-safety #memory-safety #use-after-free #double-free

Patched

no patched versions

Affected Functions

Version

sized_chunks::Chunk::clear

• <=0.7.0

sized_chunks::Chunk::drop_left

• <=0.7.0

sized_chunks::Chunk::drop_right

• <=0.7.0

sized_chunks::InlineArray::clear

• <=0.7.0

sized_chunks::RingBuffer::clear

• <=0.7.0

sized_chunks::RingBuffer::drop_left

• <=0.7.0

sized_chunks::RingBuffer::drop_right

• <=0.7.0

Description

Several methods in sized-chunks drop elements before updating the length/boundary metadata. If an element's Drop panics during the drop, the metadata update is skipped, so the container still treats the already-dropped elements as live. When the container's own Drop runs, those elements are visited again — a use-after-free / double-free reachable from safe Rust.

The RingBuffer methods require the ringbuffer feature. This is distinct from RUSTSEC-2020-0041 (Chunk::clone / insert_from, fixed in 0.6.3); the methods here are still affected in 0.7.0. The repository is archived with issues/PRs disabled and no fix available.

Impact

• CWE-415 (Double Free): the same allocation is freed twice.
• CWE-416 (Use-After-Free): a freed allocation is accessed during a repeated Drop.

Reachable entirely from safe Rust via catch_unwind with element types whose Drop can panic.

Advisory available under CC0-1.0 license.