I’m super excited about this blogpost. The approach is so counterintuitive, and yet the results are so much better than anything else that we’ve tried for memory safety. We finally understand why.

https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html

Eliminating Memory Safety Vulnerabilities at the Source

Posted by Jeff Vander Stoep - Android team, and Alex Rebert - Security Foundations Memory safety vulnerabilities remain a pervasive threa...

Google Online Security Blog
@jeffvanderstoep Yes, concentrating on making the new code safer makes ton of sense. The only part that I find dubious is that bug in old code decay exponentially over time. I remember when new issues like integer overflow became mainstream, leading to tons of new bugs discovered in very old code. We are always at risk of the next attack method preying on unaware old code.