Ode to the use-after-free: one vulnerable function, a thousand possibilities
I think the generalization of &quot;use-after-free&quot; to &quot;use-after-invalidation&quot; is the most important part of this article, showing that it&#x27;s more about object &quot;lifetimes&quot; than simply a memory management flaw. This is one reason why we can&#x27;t consider &quot;modern C++&quot; to be memory-safe.<p>I wonder if this sort of vulnerability is possible in Rust, and if it is, is there a way to use Rust&#x27;s borrow checker to make it impossible?