Re:Linux Kernel Use-After-Free Remote Code Execution Vulnera...
by fulafel on Wednesday October 05, 2016 @01:14AM
(#12641690)
Here's my attempt at a constructive idea, inspired by all the preemptive C comments:
The l-k devs and the big commercial Linux vendors/users (Google, IBM, Red Hat, Amazon etc) should gang up and start offering big bounties for these. And simultaenously start doing subsystem rewrites in a memory-safe way prioritized by bugs found by bounty program (and other ways). If they're allergic to non-C languages, a safe C subset like SAFEcode or C0 could be used[1].
[1] I'm saying it's possible to have a memory safe C subset with current compiler technology, even though you can point out something missing from C0
The l-k devs and the big commercial Linux vendors/users (Google, IBM, Red Hat, Amazon etc) should gang up and start offering big bounties for these. And simultaenously start doing subsystem rewrites in a memory-safe way prioritized by bugs found by bounty program (and other ways). If they're allergic to non-C languages, a safe C subset like SAFEcode or C0 could be used[1].
[1] I'm saying it's possible to have a memory safe C subset with current compiler technology, even though you can point out something missing from C0