Pull down to refresh stories
Emerging

Rust will save Linux from AI, says Greg Kroah-Hartman: why this signal is getting harder to ignore

At the Rust Week conference , the world's biggest Rust language conference, in Utrecht, Netherlands, Linux stable kernel maintainer Greg Kroah-Hartman opened by saying: "I'm here to talk about untrusted data and Linux, and how Rust is going to save us ." After "a long month or two on the kernel security list," he pushed that point even further: "I'm going to make even a bolder statement and say, 'You are going to save Linux.' Sorry, it's all on you.". As a result, Kroah-Hartman, who has "seen every single kernel security bug ever" since 2005, said the kernel team is now issuing "13 CVEs [Common Vulnerabilities and Exposures] a day, or something, something crazy." He thinks Rust is one of the few realistic ways to slash the class of bugs that come from C's traditional error-handling and resource-management pitfalls. This piece sits on 1 source layers, but the real value is showing why the story should not be skimmed past too quickly.

At the Rust Week conference , the world's biggest Rust language conference, in Utrecht, Netherlands, Linux stable kernel maintainer Greg Kroah-Hartman opened by saying: "I'm here to talk about untrusted data and Linux, and how Rust is going to save us ." After "a long month or two on the kernel security list," he pushed that point even further: "I'm going to make even a bolder statement and say, 'You are going to save Linux.' Sorry, it's all on you.". As a result, Kroah-Hartman, who has "seen every single kernel security bug ever" since 2005, said the kernel team is now issuing "13 CVEs [Common Vulnerabilities and Exposures] a day, or something, something crazy." He thinks Rust is one of the few realistic ways to slash the class of bugs that come from C's traditional error-handling and resource-management pitfalls. The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled.

Emerging The topic has initial corroboration, but the newsroom is still waiting on stronger confirmation.
Reference image for: Rust will save Linux from AI, says Greg Kroah-Hartman: why this signal is getting harder to ignore
Reference image from ZDNet AI. ZDNet AI

At the Rust Week conference , the world's biggest Rust language conference, in Utrecht, Netherlands, Linux stable kernel maintainer Greg Kroah-Hartman opened by saying: "I'm here to talk about untrusted data and Linux, and how Rust is going to save us ." After "a long month or two on the kernel security list," he pushed that point even further: "I'm going to make even a bolder statement and say, 'You are going to save Linux.' Sorry, it's all on you.". As a result, Kroah-Hartman, who has "seen every single kernel security bug ever" since 2005, said the kernel team is now issuing "13 CVEs [Common Vulnerabilities and Exposures] a day, or something, something crazy." He thinks Rust is one of the few realistic ways to slash the class of bugs that come from C's traditional error-handling and resource-management pitfalls. Also: One of the most user-friendly Linux distros I've ever used is also one of the most secure. ZDNet AI is the main source layer for now, and the rest should be read as a signal that is still widening. In security, the real value is not just the warning itself but the way it changes operational risk, account safety, and the cost of responding later.

What is happening now

At the Rust Week conference , the world's biggest Rust language conference, in Utrecht, Netherlands, Linux stable kernel maintainer Greg Kroah-Hartman opened by saying: "I'm here to talk about untrusted data and Linux, and how Rust is going to save us . " After "a long month or two on the kernel security list," he pushed that point even further: "I'm going to make even a bolder statement and say, 'You are going to save Linux. ' Sorry, it's all on you. ZDNet AI form the main source layer behind the core facts in this piece.

Where the sources line up

ZDNet AI is the main source layer for now, and the rest should be read as a signal that is still widening. As a result, Kroah-Hartman, who has "seen every single kernel security bug ever" since 2005, said the kernel team is now issuing "13 CVEs [Common Vulnerabilities and Exposures] a day, or something, something crazy. " He thinks Rust is one of the few realistic ways to slash the class of bugs that come from C's traditional error-handling and resource-management pitfalls. ZDNet AI form the main source layer behind the core facts in this piece.

The details worth keeping

Also: One of the most user-friendly Linux distros I've ever used is also one of the most secure. In security, the real value is not just the warning itself but the way it changes operational risk, account safety, and the cost of responding later. The people who should read carefully are system admins, shop owners, content teams, and anyone holding customer data or operational accounts. The next step is to see whether the current signals harden into a durable change or fade as a short-lived experiment.

Why this matters most

The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled. With 1 source layers on the table, the part worth reading most closely is where firm facts meet the market's early reaction. Kroah-Hartman illustrated those pitfalls with real C bugs in the kernel, including a 15-year-old Bluetooth bug that dereferenced a pointer without checking it and a Xen bug where "we forgot to unlock" in an error path.

What to watch next

The next layer to watch is scope, patch speed, and the operating cost if teams are forced to change process because of this story. Patrick Tech Media will keep checking rollout speed, user reaction, and how ZDNet AI update the next pieces. From 3 early signals, the piece keeps 1 references that are useful for locking the main details in place. That is why the useful reading move is not to stop at the headline, but to compare the promise, the workflow change, and the likely cost before deciding anything.

Source notes