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

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

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