{"id":"RUSTSEC-2026-0256","revision":"642a86a89c854162b3ff0c277797f8c2","records":[{"revision":"642a86a89c854162b3ff0c277797f8c2","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2026-0256","aliases":[],"title":"Panic-safety unsoundness in `truncate_back`, `truncate_front`, `clear`, and `extend_from_slice` (use-after-free / double-free)","description":"Several methods in `circular-buffer` drop elements before updating the buffer's start/end metadata. If an element's `Drop` panics during the drop, the metadata update is skipped, so the buffer still treats the already-dropped elements as live. When the buffer is later dropped (or used after the panic is caught), those elements are visited again — a use-after-free / double-free reachable from safe Rust.\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.\n\n## Fix\n\nFixed in `circular-buffer` 2.0.1 by adjusting the buffer's start/end metadata before the elements are dropped.","state":0,"publishedAt":"2026-08-11T12:00:00+00:00","modifiedAt":"2026-08-12T10:30:20.5903207+00:00","affected":[{"ecosystem":"crates.io","name":"circular-buffer","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"},{"kind":"fixed","version":"2.0.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/circular-buffer","https://rustsec.org/advisories/RUSTSEC-2026-0256.html","https://github.com/andreacorbellini/rust-circular-buffer/blob/master/CHANGELOG.md"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2026-0256","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2026-0256","identifiers":["RUSTSEC-2026-0256"]},"retained":false,"historicalAffected":[]}],"coverage":[]}