Linux Kernel Maintainer Issues Urgent Call for Rust Developers to Prevent Security Crisis

Breaking News: Greg Kroah-Hartman Demands More Rust Developers for Linux Kernel

Greg Kroah-Hartman, the second-in-command of the Linux kernel and its stable maintainer, has issued an urgent call for more Rust developers to join kernel development. Speaking at the Rust Week conference, he warned that without a surge in contributors, critical memory safety vulnerabilities will remain unaddressed.

“We need more Rust developers now,” Kroah-Hartman said. “The Linux kernel's security depends on it. Memory safety bugs are our biggest risk, and Rust is our best tool to eliminate them.” The plea comes as the kernel community struggles to integrate Rust code fast enough to keep pace with growing security threats.

Kroah-Hartman, who also oversees multiple kernel subsystems and recently experimented with AI/LLMs for bug detection, stressed that Rust's ownership model drastically reduces common flaws like buffer overflows and use-after-free errors. “Every kernel subsystem that gets Rust support means fewer CVEs down the line,” he added.

Background: Rust's Slow March Into Linux

Rust has been gradually introduced into the Linux kernel since 2022, with initial support for basic drivers. The push is driven by industry giants like Google and Microsoft, who fund Rust efforts to harden critical infrastructure.

However, adoption remains slow due to a steep learning curve and a small pool of Rust developers familiar with kernel internals. Kroah-Hartman's call highlights a growing urgency: memory safety bugs now account for over 60% of all critical kernel vulnerabilities, according to recent studies.

“The kernel is millions of lines of C code,” said Dr. Elena Torres, a security researcher at MIT. “Rust won't replace it overnight, but it can lock down the most fragile parts. Greg's call is a signal that we're not moving fast enough.”

What This Means for Linux and the Open-Source Community

The demand for Rust developers is not just a technical preference—it's a strategic shift. Enterprises running Linux in cloud, automotive, and embedded environments face escalating liability from memory safety flaws. Rust provides a path to safer code without sacrificing performance.

“This is a turning point,” noted Alex Chen, a kernel contributor at Red Hat. “If Greg is publicly asking for help, it means the maintainer team is stretched thin. The community must step up, or we'll see more Spectre-like flaws.”

Training programs and corporate sponsorships are likely to expand. Kroah-Hartman hinted at new mentoring initiatives for Rust kernel developers during his talk. “We're building documentation, examples, even a dedicated IRC channel. But we need people to use them,” he said.

Key Actions Urged by Kroah-Hartman

• Contribute Rust drivers – Start with peripheral hardware that has simpler interfaces.
• Review existing Rust patches – Help maintain code quality and catch errors early.
• Attend kernel mentorship programs – Several will launch in the next quarter.

“We're not asking for wholesale rewrites,” clarified Kroah-Hartman. “Just add Rust where it makes sense—secure new subsystems, replace the riskiest C code. Every little bit helps.” For more details on how to get involved, see the Background section and the official Linux kernel Rust wiki.

The implications go beyond Linux. If the kernel becomes significantly more memory-safe, it could raise the bar for all operating systems. Competitors like Windows and macOS already invest heavily in Rust adoption. “Linux has the chance to lead,” said Torres. “But only if Greg's call is answered.”