Add unsound advisory for stack_dst

[tooson9010-spec]

Affected crate(s)

• stack_dst (5,257 recent downloads per crates.io)

Links to upstream issue(s) or PR(s)

thepowersgang/stack_dst-rs#16

Severity

Three removal/replacement paths destroy an initialized value before committing the metadata change that removes it. A panicking T::drop() skips the commit, so the container still treats the destroyed value as live and drops it again — use-after-free / double-free reachable from safe Rust, confirmed under AddressSanitizer on all three paths. Separate from RUSTSEC-2021-0033, which covered push_cloned. Fixed in 0.8.2.

Checklist

• Advisory filename(s) starts with RUSTSEC-0000-0000 as the ID
• date field is set to the public disclosure date
• Contains a concise and descriptive title after advisory metadata
• Asked maintainer(s) if publishing an advisory is appropriate (asked on the issue; the maintainer approved with a 👍 reaction)