The release candidate itself was unremarkable in the best way: another week of bug and regression fixes across drivers, networking, and filesystems, the usual late-cycle tightening. But read Linus Torvalds' announcements across the whole 7.3 cycle and a pattern jumps out that has nothing to do with any single subsystem. The kernel's development rhythm has changed, and everybody involved knows what changed it.

The joke that wasn't really a joke

Back at 7.3-rc2, Torvalds noted that the release "didn't feel like a particularly busy rc2, but it clearly was" — rc2 is usually the quietest point in the cycle, the breather after the merge window. This time it arrived "full fat": filesystems, a sizable DRM pull, networking, BPF, and driver trees all landing fixes at once.

He couldn't find a single cause. Then came the line everyone quoted: "we'll obviously all blame it on AI, because whether that's really the cause or not, it's an easy thing to blame ;)"

It reads like a joke. The winky face is doing a lot of work. But two months earlier, announcing 7.2-rc7, Torvalds had already sounded resigned rather than amused: "it is what it is: the new normal with a lot of fixes, many of them due to review by various AI tools." That candidate carried more than 400 fixes from upwards of 230 contributors — numbers that used to belong to the opening merge window, now arriving late in the stabilization phase.

The numbers behind the shrug

The anecdotes stack up fast once you look:

  • Networking maintainer Jakub Kicinski reported that between one-third and one-half of the patches flowing through the net-next tree during the 7.3 cycle appeared tied to automated or AI-driven cleanups — many needing human triage to separate signal from noise.
  • In May 2026, Torvalds declared the kernel's private security mailing list almost entirely unmanageable: duplicate reports generated by AI tools creating pointless churn. His ask was blunt — read the documentation, test your findings, submit real patches instead of raw output.
  • At Kernel Recipes 2026, Greg Kroah-Hartman took the stage to talk about how the kernel security team is handling the deluge of LLM-generated bug reports. His core message, per LWN's coverage: "don't panic."

And the fixes themselves tell the story. The seven-stable-release batch of October 3 was heavy on memory-safety bugs — use-after-free, out-of-bounds reads, NULL dereferences — with commit messages carrying attributions to syzbot, fuzzing pipelines, static analysis, and the occasional honest "Assisted-by: LLM" line. The machines find the bugs. Humans still review every patch. That division of labor is now the normal state of kernel development.

The rules of the new assembly line

The kernel community hasn't just accepted this — it has started legislating it. The project's guidance on AI coding tools settled on a principle that is almost elegant in its brevity: AI can assist; AI cannot assume ownership. A human must stand behind every change, understand it, and take responsibility for it. There is even ongoing work on better prompts for AI-assisted code review, because if the machines are going to read the code, they might as well be told how the project wants it read.

This is the part worth sitting with. The kernel is 30+ million lines of C maintained by thousands of humans, and it has now formally become a human-machine assembly line: automated tools scan at a scale no human can match, surface the error-path bugs human eyes glide past, and human maintainers act as the final gate. The FreeVxFS filesystem driver got removed this year after its maintainer concluded the code had become little more than target practice for automated checkers — a small casualty that says everything about where the pressure lands.

The operator's take

So what does the "AI normal" change for you, the person running the kernel rather than writing it?

Mostly, it's good news wearing a boring disguise. The flood is dominated by small error-path fixes: missing NULL checks, wrong error codes on unlikely paths, off-by-one bounds. These are the bugs that become oopses, panics, and — occasionally — privilege escalations. A kernel that receives hundreds of these fixes per cycle is a kernel getting measurably harder to crash. The unglamorous grind is the whole point.

Expect bigger patch sets, more often. Greg Kroah-Hartman has noted the kernel's CVE count climbing past 1,500 in recent cycles and heading toward 2,000. That is not the kernel getting less safe — it is the kernel getting more examined. But it does mean your distro's security updates will keep arriving in a steadier drumbeat. Keep the updates flowing and reboot on purpose; the machines found the bugs so you don't have to find them the hard way.

Noise is part of the deal. When patch volume goes up, so does the occasional revert — a fix that looked obvious but wasn't. That's the review burden maintainers keep warning about, and it's the price of the assembly line. Running a distribution kernel rather than mainline is, among other things, a way of letting someone else absorb that noise.

If you file bugs, file good ones. The security list doesn't need more raw tool output. Test your finding, write the patch if you can, and a human will take it from there. In the AI normal, the scarcest resource isn't bug discovery — it's maintainer attention.

The 7.3 cycle will be remembered, if it's remembered at all, as the one where nobody pretended anymore. The kernel is co-debugged by machines now. Your part of the contract hasn't changed: update, reboot, and let the assembly line do its work.

Sources: kernel.org (7.3-rc6 release date verified on the official front page) · The Register — "Might as well blame AI for this giant Linux release candidate, says Linus Torvalds" (Sep 7, 2026) · WebProNews — "Linus Torvalds Accepts Oversized Linux Kernel Releases as AI-Driven Reality" · WebProNews — "Linux Kernel Sets Strict Rules for AI Coding Tools as Contributors Embrace the Technology" · LWN.net — "Coping with the onslaught of kernel security bugs" (Oct 1, 2026) · OSTechNix — "Linux Kernel 7.3 RC5 is Officially Released" (release timeline) · Linux News — "Linux 7.3-rc6 Released: Normal For The New 'AI Normal'"