A better link might be to the security properties (it is linked from the current page). <a href="https://github.com/struct/isoalloc/blob/master/README.md#security-properties" rel="nofollow">https://github.com/struct/isoalloc/blob/master/README.md#sec...</a><p>It sounds a little bit like ElectricFence, although that project was more focused on finding memory bugs rather than security.<p>It would be good to consider which of these features is lightweight enough that it might be pulled into the glibc allocator. glibc is already doing good work with various hardening features (<a href="https://access.redhat.com/blogs/766093/posts/1976213" rel="nofollow">https://access.redhat.com/blogs/766093/posts/1976213</a>). However I don't think they PROT_NONE internal data structures yet.