4 ms·
I really shouldn't comment on Linux kernel development, given mu lack of knowledge, but since this is a use-after-free vuln, doesn't that strengthen the case to
by SilasX 8y ago
I really shouldn't comment on Linux kernel development, given mu lack of knowledge, but since this is a use-after-free vuln, doesn't that strengthen the case to moving to memory safe languages?
- saagarjha 8y agoThe Linux kernel has far too much C for this to be easy to do.
- IAmLiterallyAB 8y agoPerhaps a language that supports a C FFI, like Rust. Of course, Rust is probably not mature enough to be used in the kernel.
- yjftsjthsd-h 8y agoWhy isnt it mature enough? Redox seems like an argument that it can work. Granted, there are general issues with requiring a new compiler, etc.
- FartyMcFarter 8y agoDoes Rust support all the platforms the Linux kernel is available for?
- steveklabnik 8y agoNo.
- exabrial 8y agoYou would take a massive hit in performance. But there are operating systems (some commercial) like that
- SilasX 8y agoWhat about Rust?
- pjmlp 8y agoIncluding Android and ChromeOS, which while being based on the Linux kernel don't expose its interfaces directly to userspace, and with Treble Android Linux variant is a kind a pseudo micro-kernel with several services running on their own processes and using Android IPC for data exchange.
- apta 8y agoNot really. See Rust or D.
- pcwalton 8y agoAlong with the innumerable other bugs like it, yes.
- pjmlp 8y agoIt very hard to do that, because UNIX and C go hand in hand. Moving away from C, which is a good thing on my opinion, would ultimately mean moving away from UNIX, as those OSes have other cultures. So what we really need, since UNIX based OSes aren't going away that fast, is to tame C. Solaris already did this with hardware memory tagging when running on SPARC. On Solaris/SPARC an use-after-free attempt would terminate the process, or in this case trigger a kernel panic. Google has been pushing for the Kernel Self Protection Project[1]. One of such initiatives is collaboration with ARM for hardware memory tagging on ARM v8.5[2]. Intel had MPX, but apparently it didn't took over and now is scheduled for removal, leaving SPARC and future ARM releases as the only architectures where it is possible to have some hardware control over C memory accesses. [1] - https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Pr... [2] - https://community.arm.com/processors/b/blog/posts/arm-a-profile-architecture-2018-developments-armv85a https://community.arm.com/processors/b/blog/posts/arm-a-prof...