Add advisory for sized-chunks: panic-safety UAF/double-free in clear/drop_left/drop_right - #3111
Conversation
…drop_left/drop_right
|
Thanks for the reply. I saw #3093 adds the unmaintained advisory for sized-chunks. This PR (#3111) is the companion informational = "unsound" advisory you mentioned
Happy to adjust this to fit alongside #3093 however works best. |
|
While doing research on panic-safety unsoundness, I found the same issue in Since it's a separate crate under a different owner, would a separate |
|
Yes, a separate advisory would be the way to go. Use the pull request template both for this advisory and for the other one. |
Simplify sized-chunks advisory
|
Thanks. I've updated the PR description to follow the template. The separate advisory for sp-sized-chunks is filed in #3136. |
add affected.functions
Affected crate(s)
sized-chunks0.7.0 (6,946,615 recent downloads per crates.io)Links to upstream issue(s) or PR(s)
The repo is archived with issues/PRs disabled. I emailed the maintainer on 2026-04-22 with no response. Unmaintained status is tracked in #3058 / #3093.
Severity
Panic-safety unsoundness in
Chunk,RingBuffer, andInlineArray(clear,drop_left,drop_right,InlineArray::clear). Elements are dropped before the length/boundary metadata is updated, so a panicking elementDropleaves stale metadata and the container's ownDropre-drops already-freed elements — use-after-free / double-free reachable from safe Rust, confirmed under AddressSanitizer. Distinct from RUSTSEC-2020-0041 (Chunk::clone/insert_from, fixed in 0.6.3); still affected in 0.7.0.Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure date