inb4: - Nooo, my performance. - Well if you'd care about performance, you also wouldn't be duplicating lists/strings to make sublists/substrings all the time.
@lanodan@queer.hacktivis.me@chjara@akko.wtf There are many well-known mitigation techniques, like memory poisoning, and have already existed for 10+ years. But many are very aggressive (to them, Linux is exploitable despite some mitigations because they're too half-assed). Meanwhile kernel developers don't like them and think they're either too invasive or too paranoid (e.g. In PaX, you must call pax_open_kernel() whenever you need to change a critical kernel data structure). Linus in particular, hates security people and think they're mostly impractical jerks.
@lanodan@queer.hacktivis.me@chjara@akko.wtf For the note, PaX supported zero-poison after free (PAX_MEMORY_SANITIZE) since the year 2010. But of course LKML and PaX Team hate each other so it took 7 years before the Google / Kees Cook gang pushed it for upstreaming.