Attacking Android Binder

I'd love to have this in-depth level of knowledge of kernel inner workings. Super interesting writeup.

And again an extremely serious, device-compromising vulnerability, arises from a use-after-free. When will we learn?<p>I don&#x27;t think I&#x27;ll ever be able to trust modern devices until we finally abandon memory-unsafe languages. It&#x27;s such low hanging fruit at this point I don&#x27;t understand anymore why OS developers keep investing their time in other parts of the threat model of operating systems if memory usage vulnerabilities keep arising that completely destroy the existence of any security layer in the system.<p>Was Google&#x27;s plan to replace Android with Fuchsia? Is there any plan to get rid of these vulnerabilities (specially use-after-free) at scale on Android like the Chrome project has attempted with the MiraclePtr project?

&gt; The motivation for this design is that a client can send a transaction and then wait for a response with one ioctl syscall. In contrast, IPC with sockets requires two syscalls, send and recv.<p>What a great motivation. Oh wait, then you write your literal operating system and all services in Java of all languages.<p>I find Android&#x27;s architecture so frustrating, all the wrong design decisions