Linux Kernel Rust Code Sees Its First CVE Vulnerability
Linux Kernel Rust Code Sees Its First CVE Vulnerability

Linux Kernel Rust Code Sees Its First CVE Vulnerability

No one said rust was invulnerable.
I think the other takeaway here is that it was found in a section marked "unsafe". At the very least, that's a useful tool for the Devs to isolate potential problem areas. Comparing that to a pure C codebase where the problem could be anywhere.
The funny part is: the fix does not change the unsafe block at all. The issue is elsewhere in safe rust code.
doesn't change anything if you can't avoid having to write the unsafe parts
Boone? There are plenty of fan boys out there that are selling rust like AI, or in other words snake oil.
Rust obviously has built in securities that C doesn't have, but a shitty coder is a shitty coder and bad QC is bad QC. Now we're seeing the reality of the consequences.
Rust and/or other memory safe(r) languages are like the future, but hopefully more people are now seeing the cracks. Just look at cloudflare for a prime example.
the cloudflare issues were configuration… they have nothing even remotely relayed to any of this
JavaScript would have prevented this.
You're so right! The Linux kernel should be re-written as a Deno executable
Sucks to be the person who made that commit. Genuinely.
Back luck Brian kernel developer.
Surprised it took so long.
almost as if using a memory safe language actually reduces the CVEs related to memory
What's the point of rewriting parts of the kernel in unsafe rust?
Because Rust lets you choose when something is unsafe vs writing all unsafe in code all the time:
Note the other 159 kernel CVEs issued today for fixes in the C portion of the codebase
Yes same concept as other languages like C#
I wonder if this can be adjusted for LoC count in each language
it's not like the whole driver is written in unsafe rust
Mostly to attract new, younger kernel maintainers.
That's legitimately a good reason. They can pry my C from my cold dead hands...but someday someone will have to. May as well think about what that should look like.
unsafe is usually used only when you need to interact with something else like low level or ffi
Because Rust is the popular thing in FOSS/Linux at the moment.
For memory safety, which is not unsafe rust