News for hackers. Stuff that matters.
Re:Local privilege escalation vulnerabilities in Linux by Muromec on Wednesday November 04, 2026 @08:14PM (#50373762)
Kernel will eventually move to rust, but not the dramatic and fast way
Re:Local privilege escalation vulnerabilities in Linux by shoobiedoo on Wednesday November 04, 2026 @08:30PM (#50373891)
Won't AI's ability to discover these bugs reduce the need to rewrite things in rust? If the major benefit to rewriting them is memory safety, I mean...
Re:Local privilege escalation vulnerabilities in Linux by Gigachad on Wednesday November 04, 2026 @08:52PM (#50374077)
That's assuming the current models are able to find all the bugs, and that we won't have a better model out every few months that will be able to find even more obscure bugs.

We would also have to burn a trillion tokens a day verifying all the C code the hard way forever going forward. It would be cheaper to rewrite the kernel in Rust, subsystem and driver by driver at a time.

Re:Local privilege escalation vulnerabilities in Linux by shoobiedoo on Wednesday November 04, 2026 @09:14PM (#50374246)
I see. Fair enough
Re:Local privilege escalation vulnerabilities in Linux by est31 on Wednesday November 04, 2026 @09:21PM (#50374301)
That's a fair question, and actually one I ask myself too.

AI doesn't give a strong guarantee that things work though, while Rust gives a much stronger (not absolute) guarantee.

But maybe the way of the future is to auto-generate proofs that the code is memory safe. The C code and the AI generated proofs could live separately and so it would need less maintainer buy-in.

Re:Local privilege escalation vulnerabilities in Linux by imtringued on Thursday November 05, 2026 @08:50AM (#50379049)
I'm thinking a language change isn't enough... At least not for a kernel.

There has to be a pseudo userspace type of way to build a kernel driver. Basically, user space programs are fine, but kernel drivers need their own form of encapsulation without expensive context switches.

Something like memory encryption or memory access bounds. During the handoff you do not change the address space, you just restrict access to a subset of the kernel memory.

Re:Local privilege escalation vulnerabilities in Linux by Muromec on Friday November 06, 2026 @05:49AM (#50390741)
You could in principle use LLM as a formatter, linter and a borrow checker, but an actual linter, formatter and rust compiler are still faster and cheaper to run on a million lines of code. They are more reliable too because of context size limits and attention thingy (read those thinking traces when it approaches 1M limit an fucks up tool calls -- you will get the sleep deprived person vibes from it).

So first you would run the three above to pick the low hanging fruit and then ask the shaitan in a box to find more bugs. Looking from another angle -- rust is another a tool AI can use to find memory bugs, so why not have rust.

Then again, I asked the thing to write some C (more or less from scratch) few weeks ago and the next time I looked it was chasing segfaults and wondering where they came from.