{"id":"RUSTSEC-2026-0254","revision":"f2b2a640f2ab4e4fa30333a27761c440","records":[{"revision":"f2b2a640f2ab4e4fa30333a27761c440","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2026-0254","aliases":[],"title":"Panic-safety unsoundness in `Chunk` and `InlineArray` (use-after-free / double-free)","description":"Several methods in `sp-sized-chunks` drop elements before updating the container's 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 is later dropped, its own `Drop` re-visits those slots and drops the freed elements again — a use-after-free / double-free reachable from safe Rust.\n\n`sp-sized-chunks` is a fork of `sized-chunks` (companion advisory filed separately) and carries the same bug. The repository is archived and the crate is still on 0.1.0 with no fix available.\n\n## Impact\n\n- **CWE-415 (Double Free):** the same allocation is freed twice (e.g. an element holding `Box<T>`).\n- **CWE-416 (Use-After-Free):** an element reads its own freed allocation during `Drop` (e.g. `String`) — confirmed under AddressSanitizer.\n\nAll are reachable 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:15.0552424+00:00","affected":[{"ecosystem":"crates.io","name":"sp-sized-chunks","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/sp-sized-chunks","https://rustsec.org/advisories/RUSTSEC-2026-0254.html"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2026-0254","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2026-0254","identifiers":["RUSTSEC-2026-0254"]},"retained":false,"historicalAffected":[]}],"coverage":[]}