Torvalds AI Code Disclosure: a Cybersecurity Check

Linux is dropping its AI "Assisted-by" tag — and Linus Torvalds called AI disclosure rules "utterly stupid." His argument: what matters is whether someone understands the code, not which tool wrote it. Meanwhile, AI is finding real security bugs in 20-year-old drivers and stressing maintainers to the breaking point. This free check scores whether your AI-code review process is sound. No signup, nothing installed.

October 2026 update: the man who mocked disclosure rules used AI himself

What happened

What Torvalds said (attributed, not endorsed)

The two-sided security picture

Honest takeaway — Torvalds' core principle

Strip away the personalities and the debate reduces to one principle: review the code, not the provenance. A label saying "AI wrote this" tells you nothing about whether it's correct or secure — and a human-written patch can be just as broken. What protects you is a review process where a human who understands the code actually reads it. The tag died; accountability didn't — the human still owns every submitted line, and nobody gets to hide behind "the AI wrote it." That principle is what the quiz below tests.

The 5-question check: is your AI-code review process sound?

Cybersecurity FAQ

What is the Linux kernel's Assisted-by tag?

Since January 2026, contributors using advanced coding tools were asked to declare it with an "Assisted-by" tag in commits. After the 2026 Maintainers Summit it is being deprecated, with Sasha Levin's October 9 patch proposing to remove the documentation.

Why did Torvalds call AI disclosure rules "utterly stupid"?

His argument: understanding code has very little to do with the tools used to write it, so mandating tool disclosure misses the point. He illustrated it by joking that contributors might as well drop compilers and write in assembler.

What does "bots talking to bots" mean for review quality?

Agentic systems like Sashiko now review kernel patches on the mailing list, and some maintainers expect patches to have passed through them — so AI-written code is increasingly pre-reviewed by AI, thinning the human layer.

Does AI actually improve the Linux kernel?

Torvalds says yes on balance — AI finds genuine flaws, even in 20-year-old drivers. But it also stresses maintainers severely, and he urges caution for anything "real and important."

Which projects ban AI-generated code?

System76 banned AI-generated content from its COSMIC desktop, and NetBSD has banned AI-generated code since 2024 — the industry is split between bans, disclosure, and Torvalds' review-the-code position.

Did Torvalds use AI on the kernel himself?

Yes — days before mocking disclosure rules, he pushed a branch (noref-filemap-read-with-llm) whose code, test programs, review, and cover-letter draft were produced with Claude Code under his supervision, and fixed 2013-era bugs in assoc_array with LLM help, writing that he "did what I preach." Neither had merged as of mid-October.

If the tag is gone, what accountability is left?

Everything that actually mattered: only humans can add Signed-off-by and certify the Developer Certificate of Origin, the submitter reviews all AI-generated code and takes full responsibility, and code must be GPL-2.0-only. The tag died; the human's ownership of every submitted line didn't.

Honest scope

Featured platform — Vibe-Code Audit: Vibe-Code Audit — security auditing for AI-written code. Because the debate is settled one way or another, the code still needs auditing.

Get early access on WhatsApp →

FROM INGENIOUS AI — all 11 platforms: DisclosureGuard · ModelMinder · TermsWatch · Vibe-Code Audit · Rogue-Agent Defense · BreachHunter · ChatBreaker · Agent Flight Recorder · Agent Auth Gateway · DomainGuard · ContentCraft AI

Related checks