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.
Drop.Reachable entirely from safe Rust via catch_unwind with element types whose Drop can panic.
{
"license": "CC0-1.0"
}{
"affects": {
"os": [],
"functions": [
"sized_chunks::Chunk::clear",
"sized_chunks::Chunk::drop_left",
"sized_chunks::Chunk::drop_right",
"sized_chunks::InlineArray::clear",
"sized_chunks::RingBuffer::clear",
"sized_chunks::RingBuffer::drop_left",
"sized_chunks::RingBuffer::drop_right"
],
"arch": []
},
"affected_functions": null
}