{"id":"RUSTSEC-2026-0255","revision":"d6a2a63de92a435ab308f5cd894e4328","records":[{"revision":"d6a2a63de92a435ab308f5cd894e4328","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2026-0255","aliases":[],"title":"Panic-safety unsoundness in `Chunk`, `RingBuffer`, and `InlineArray` (use-after-free / double-free)","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.\n\nThe `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.\n\n## Impact\n\n- **CWE-415 (Double Free):** the same allocation is freed twice.\n- **CWE-416 (Use-After-Free):** a freed allocation is accessed during a repeated `Drop`.\n\nReachable entirely from safe Rust via `catch_unwind` with element types whose `Drop` can panic.","state":0,"publishedAt":"2026-08-11T12:00:00+00:00","modifiedAt":"2026-08-12T10:30:03.0789962+00:00","affected":[{"ecosystem":"crates.io","name":"sized-chunks","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/sized-chunks","https://rustsec.org/advisories/RUSTSEC-2026-0255.html"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2026-0255","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2026-0255","identifiers":["RUSTSEC-2026-0255"]},"retained":false,"historicalAffected":[]}],"coverage":[]}