News for hackers. Stuff that matters.
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @01:56PM (#46303856)
I've written lots of `forbid(unsafe_code)` in Rust; it depends on where in the stack you are and what you're doing.

But as the adjacent commenter notes: having unsafe is not inherently a problem. You need unsafe Rust to interact with C and C++, because they're not safe by construction. This is a good thing!

Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by informa23 on Wednesday December 17, 2025 @02:06PM (#46304025)
EDIT: Hacker News has limited my ability to respond. Please keep in mind that Rust has a large number of active fans, who may have biases for whatever reasons.

Do you agree or disagree with

https://www.reddit.com/r/rust/comments/16i8lo2/how_unpleasan...

> It is worse than writing equivalent unsafe code in, say, C. The main pain point is that Rust has a rather complicated relationship between raw pointers and non-raw pointers (mainly references and box). Namely is how they invalidate each other. A good rule of thumb is to mix them as little as possible. But eventually the raw-pointer-heavy unsafe code will have to interface with reference-heavy safe code, and that's where the tricky stuff is.

> Unsafe Rust is generally much harder to get right than unsafe C or unsafe C++. There's no sugar coating it. Rust relies on many more invariants and guarantees that you have to account for than C or C++ do, so there's much more mental overhead.

matthieum, a Rust reddit mod and fan of Rust, disagrees with those posts. Whether he is biased or not is up to others to decide.

Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @02:14PM (#46304130)
I think unsafe Rust is harder to write than C. However, that's because unsafe Rust makes you think about the invariants that you'd need to preserve in a correct C program, so it's no harder to write than correct C.

In other words: unsafe Rust is harder, but only in an apples-and-oranges sense. If you compare it to the same diligence you'd need to exercise in writing safer C, it would be about the same.

Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by jackrabbit1997 on Wednesday December 17, 2025 @02:24PM (#46304265)
How would you describe the aliasing requirements of C and Rust, and do you consider them the same, as well as equally difficult?
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @02:30PM (#46304343)
Safe Rust has more strict aliasing requirements than C, so to write sound unsafe Rust that interoperates with safe Rust you need to do more work than the equivalent C code would involve. But per above, this is the apples-and-oranges comparison: the equivalent C code will compile, but is statistically more likely to be incorrect. Moreover, it's going to be incorrect in a way that isn't localizable.
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by jackrabbit1997 on Wednesday December 17, 2025 @08:57PM (#46308109)
Are you using an LLM to write your posts?
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @09:20PM (#46308257)
No, that’s just how I write. Do you normally insinuate from green accounts?