Use-after-free in interned values and cached function results

Use-after-free when a future's Drop panics while the container is dropped

Use-after-free in clear and retain when an element's Drop panics

Double free / use-after-free in Chunk and InlineArray removal methods when an element's Drop panics

Double free / use-after-free in Consumer::skip and Consumer::clear when an element's Drop panics

Double free in OwnedAlloc::drop_in_place when the contained value's Drop panics

Double free in Map::into_iter and an uninitialized Arc in SharedIncin::clear

Double free in AlignedBox<[T]>::realloc_with_default when an element's Drop panics

Double free / use-after-free in ReadChunk::commit when an element's Drop panics

Panic-safety unsoundness in Stack::pop, Fifo::pop_front and Value::replace_stable (use-after-free / double-free)

Panic-safety unsoundness in BitVecCore::clear (double-free / use-after-free)

Panic-safety unsoundness in Chunk and InlineArray (use-after-free / double-free)

Panic-safety unsoundness in truncate_back, truncate_front, clear, and extend_from_slice (use-after-free / double-free)

Panic-safety unsoundness in Chunk, RingBuffer, and InlineArray (use-after-free / double-free)

Potential use-after-free due to lack of panic safety in LruCache::pop()

Safe ErrorRegistry APIs can cause undefined behavior

Crafted archives can cause a use-after-free during deserialization

Several memory corruption issues via safe APIs

Use-after-free

Double-free in vmem storage reachable from safe Rust (predecessor of oneringbuf)

Double-free in vmem storage reachable from safe Rust

Double-free and use-after-free in Keys::next()

Potential use-after-free due to lack of panic safety in InlineVec::clear and SerVec::clear

Use-After-Free and Double Free in IntoIter::drop When Element Drop Panics

Double-free and use-after-free for Hive

Potential use-after-free in oneshot when used asynchronously

Use After Free in lucet-runtime

Multiple soundness issues in macroquad

Risk of use-after-free in borrowed reads from Python weak references

Non-idiomatic use of iterators leads to use after free

Potential stack use-after-free in Instrumented::into_inner

Use-after-free due to a lifetime error in Vec::into_iter()

Bug in pooling instance allocator

Unsound API in secp256k1 allows use-after-free and invalid deallocation from safe code

Use after free in Neon external buffers

Use after free with externrefs and epoch interruption in Wasmtime

Unsoundness in dashmap references

Use after free in lru crate

Incorrect Lifetime Bounds on Closures in rusqlite

Multiple Vulnerabilities in Wasmtime

Use after free possible in uri::Formatter on panic

Fix a use-after-free bug in diesels Sqlite backend

Use-after-free when cloning a partially consumed Vec iterator

Use-after-free in subscript_next and subscript_prev wrappers

futures_task::waker may cause a use-after-free if used on a type that isn't 'static

Flaw in interface may drop uninitialized instance of arbitrary types

MultiDecoder::read() drops uninitialized memory of arbitrary type on panic in client code

array_queue pop_back() may cause a use-after-free

Double-free and use-after-free in SmallVec::grow()

Cloned interners may read already dropped strings