Rust Will Save Linux from AI: Greg Kroah-Hartman on C Bugs and Rust's Safety Guarantees

At Rust Week 2026, Linux stable kernel maintainer Greg Kroah-Hartman made a bold claim: Rust will save Linux from the escalating flood of AI-discovered security vulnerabilities. He cited recent serious bugs like Dirty Frag, Copy Fail, and Fragnesia as evidence that traditional C code can't keep up with automated bug-finding tools. The kernel team now issues roughly 13 CVEs per day.
Why Rust? Compile-Time Enforcement
Kroah-Hartman demonstrated with real examples: a 15-year-old Bluetooth bug that dereferenced a pointer without checking, and a Xen bug where a lock was forgotten in an error path. He estimates that 60% of kernel bugs fall into two categories: unchecked error conditions and locking errors. Rust eliminates these entirely at compile time.
He highlighted Rust's locking abstractions in the kernel: "The only way you can get access to inner pointers of structures is by grabbing that lock, and releasing the lock automatically. The compiler does it... You just can't write code to access these values without grabbing the lock." This shifts correctness checking from human review to the compiler.
Impact on C Code
Even if Rust vanished tomorrow, Kroah-Hartman said its influence has already forced Linux to adopt better C patterns: "We stole this from Rust. Thank you." New C "guards" and scoped locks inspired by Rust's ownership model now make it harder for C code to mishandle locks and memory.
With ~5,000 developers but only ~700 maintainers, review time is the bottleneck. Rust's safety guarantees let maintainers approve code faster: "If I can review your code more easily, I can glance at it and say, 'Hey, look, you obviously got it right because you use that pattern.'"
The Bottom Line
Kroah-Hartman isn't claiming Rust is magic — he's saying it directly removes the most common and dangerous bug classes. AI tools are accelerating vulnerability discovery, but Rust's compile-time checks offer a scalable defense. More Linux kernel code will be written in Rust going forward, and existing C code is being cleaned up under Rust's influence.
📖 Read the full source: HN AI Agents
👀 See Also

Seven Ways to Avoid Losing Your Job to AI – Tyler Cowen's Practical Guide
Tyler Cowen outlines seven principles, including seeking messy jobs and being wary of remote work, to protect your career against AI competition.

Claude Opus 4.6 effort=low parameter causes lazy agent behavior
When using effort=low with Claude Opus 4.6, agents made fewer tool calls, were less thorough in cross-referencing, and ignored parts of system prompts about web research. Switching to effort=medium resolved the issues.

Exploring What Files are Included in the Context Window of a Telegram Chat
Join us as we delve into understanding what files are part of a Telegram chat's context window, enhancing your operational knowledge.

AI Didn't Delete Your Database — You Did: Accountability in the Age of AI Coding Agents
A viral story blamed an AI agent for deleting a production database, but the real issue is exposing destructive API endpoints and lack of process—not the tool.