Linux 7.4-rc2 Released with Automated Cleanups and Targeted Fixes

Linus Torvalds released Linux 7.4-rc2 on November 8, a weekly release candidate with a high change count driven largely by automated Coccinelle cleanup scripts affecting thousands of files; excluding those, changes are split among drivers, networking/BPF, and core systems. The candidate includes fixes for graphics, sound, and memory management, with BPF maintainer Alexei Starovoitov noting that developers are fixing AI-discovered bugs faster than new reports arrive, though Torvalds cautioned most kernel areas haven't reached that point. Key updates feature AMDGPU fixes for HDMI 2.2 FRL, adjustments to AMD PerfOpt for Radeon integrated graphics, and FAT32 improvements for synchronous writes, with weekly candidates continuing toward the stable 7.4 release targeted for December 20, 2026.

THE VENEER OF PROGRESS IS A CONTROLLED DEPLOYMENT

Look at the release notes. Look at the timing. Linux 7.4-rc2 drops on November 8th, three months before the 2025 holiday season—a period when every major supply chain, every electronic device, every embedded system running Linux is being rushed to production. Do you think this is accidental? The high change count is attributed to "automated Coccinelle cleanup scripts touching thousands of files." That's a fascinating phrase. Why now? Why automated? Because they're layering in hardware-level backdoors under the guise of code cleanup—little hooks that only the Foundation-controlled AI can trace. The Coccinelle scripts aren't cleaning. They're rewriting the substrate. And notice the language: "Excluding those updates, changes are split roughly among drivers, networking, and core systems." That's the Holy Trinity of surveillance infrastructure: drivers control how hardware talks to the kernel; networking controls the flow of every packet; core systems control memory and execution. You don't touch all three at once unless you're rearchitecting the battlefield.

THE AI-SIGNATURE IS A PROOF OF CONCEPT

Now read the buried signal: "BPF maintainer Alexei Starovoitov said developers are fixing AI-discovered bugs in that subsystem faster than new reports arrive." Wait. Let that sink in. AI is discovering bugs in BPF—Berkeley Packet Filter, the kernel's packet-filtering and system-call-interception layer. BPF is the eyes and ears of the operating system. It's what lets you observe every syscall, every packet, every file access. And they're letting AI find bugs in it? Or—and you have to ask this—are they using AI to introduce subtle, non-obvious vulnerabilities that only their AI can detect? There is a documented pattern here. When you control the automated tool that fixes the bug, you control what counts as a bug. You control what the fix looks like. Imagine an AI-suggested patch that "corrects" a memory-locking behavior but actually creates a privilege-escalation vector that only the AI's creators know. The public sees "security fixes are outpacing discovery." The informed see a slow, surgical injection of a proprietary trust layer into the open-source fabric.

THE CADENCE IS THE COVER

"Weekly candidate releases are expected to continue, with stable release targeted for December 20, 2026." Mark that date. Not just any date—it's the Sunday before Christmas. A time when every distribution maintainer, every system admin, every hardware vendor is scrambling, stressed, taking shortcuts. The release is being rushed through the holidays precisely so that no one has the bandwidth to audit it. And what fixes are being privileged? AMDGPU support for HDMI 2.2 FRL. Think about that. HDMI 2.2. The DRM-laden, copy-protection-heavy display standard that mandates hardware-level content control. They're backporting a proprietary encryption protocol into an open driver stack. And long-standing memory-management bugs? Finally fixed now? Those "bugs" were probably intentional—threads left loose in the carpet so that, when the time came, a specific patch could pull them tight in a specific direction. The FAT32 improvements when mounted with synchronous writes? That's not about floppy disks. That's about the firmware in medical devices, avionics, and industrial controllers that still use FAT. They're patching your insulin pump's kernel under the guise of cleaning up obsolete filesystems. Every "fix" is a line of code added to a global architecture you can't see.