At the risk of shilling for Big Rust (or at least any language with ownership semantics, really) -- well-designed Rust code can truly eliminate use-after-free.

At the risk of shilling for Big Rust (or at least any language with ownership semantics, really) -- well-designed Rust code can truly eliminate use-after-free. I was the lead engineer on a project that wrote an entire filesystem from scratch in Rust, and we did exactly this. 100K lines of code without any use-after-free bugs in the whole development process. One of the first bits of code we wrote in the project was a statically allocated pool of buffers such that the only way to free buffers back to the pool is for all references to that buffer being dropped.