Linus Torvalds released Linux 7.1-rc3 on Sunday, May 10, 2026, marking the third consecutive release candidate in what has become a noticeably larger-than-average kernel development cycle. In his announcement on the Linux Kernel Mailing List, Torvalds addressed the elephant in the room: the jump in patch volume that began with Linux 7.0 is not a temporary anomaly. It is, in his words, “the new normal.”

That wasn’t a fluke brought on by a .0 release — it simply seems to be the new normal.

— Linus Torvalds, Linux Kernel Mailing List, May 10, 2026

Torvalds has previously speculated that the growing volume of weekly patch submissions could be partly attributed to developers using AI-assisted coding tools to write and submit patches at a faster pace. While he has stopped short of declaring a definitive cause, RC3 arriving at this size — well past the major version transition where cycle sizes typically shrink — strongly reinforces that hypothesis.

Networking Dominates — A Full Third of All Changes

The most striking characteristic of this release is its skew toward networking. Approximately one third of the entire rc3 diff touches the networking subsystem, split across both the core networking stack and driver-level changes. This is unusually high for a release candidate at this stage of stabilization, when the expectation is narrow bug-fix work rather than broad subsystem churn.

Notable hardware additions in the networking space include compatibility support for USB-C networking on Apple Mac computers — an area of increasing relevance as more users run Linux on Apple silicon-adjacent hardware — and dedicated support for high-end audio networking equipment from AlphaTheta (the parent company of Pioneer DJ), specifically targeting professional-grade DJ hardware.

Linux 7.1-rc3 — Key Changes at a Glance
  • ~⅓ of all patches target networking: core stack and driver layer
  • Use-after-free security fixes in Bluetooth and GPU (graphics card) drivers
  • USB-C networking compatibility added for Apple Mac computers
  • Audio support for AlphaTheta / Pioneer DJ professional equipment
  • Intel Xeon Diamond Rapids: Auto Counter Reload (ACR) enablement
  • LoongArch architecture work: KVM virtualization and interrupt handling
  • Rust language infrastructure improvements; memory safety patch increase
  • General SELinux, SMB file-sharing, and regression fixes

Security: Use-After-Free Fixes Across Bluetooth and GPU Drivers

On the security front, RC3 incorporates fixes for use-after-free vulnerabilities found in both Bluetooth subsystem code and graphics card drivers. Use-after-free flaws are among the most serious categories of memory safety bugs — they occur when a program continues to use a pointer after the memory it references has been freed, potentially allowing privilege escalation or arbitrary code execution. Their presence in high-traffic subsystems like Bluetooth and GPU drivers makes patching a priority.

The release also continues the kernel’s ongoing embrace of the Rust programming language. Rust provides memory safety guarantees at the language level — meaning entire classes of bugs, including use-after-free, become structurally impossible in well-written Rust code. As more kernel components migrate to Rust, developers expect that the manual workload of hunting and patching memory safety vulnerabilities will gradually decrease over future release cycles.

LoongArch and Intel Diamond Rapids

This release also carries meaningful progress on the LoongArch architecture — a MIPS-derived ISA developed in China by Loongson Technology and used in domestically produced processors. The 7.1-rc3 work focuses on KVM virtualization improvements and optimizations to interrupt handling mechanisms on LoongArch systems, continuing a pattern of expanding the architecture’s feature parity with x86 and ARM.

On the Intel side, RC3 enables Auto Counter Reload (ACR) support for the upcoming Xeon Diamond Rapids platform — Intel’s next-generation server processor line built on the 18A process node. This continues the steady stream of hardware bringup work that flows into each kernel cycle ahead of major platform launches.

Release Timeline

The Linux 7.1 development cycle follows its standard weekly cadence, with a new release candidate published each Sunday. Based on current trajectory, the final stable release is expected on June 7, 2026 if the cycle concludes at RC7, or June 14, 2026 if an additional RC8 is required. The next release candidate, 7.1-rc4, is scheduled for Sunday, May 17, 2026.

Apr 13, 2026
Linux 7.0 stable released
Apr 26, 2026
Linux 7.1-rc1 released; merge window closes
May 3, 2026
Linux 7.1-rc2 released
May 10, 2026
Linux 7.1-rc3 released — subject of this report
May 17, 2026
Linux 7.1-rc4 expected
Jun 7–14, 2026
Linux 7.1 stable release expected (RC7 or RC8)
⚠ Fact-Check Note

Some earlier reporting on this release incorrectly stated the date as May 1, 2026. The correct release date is May 10, 2026. Additionally, some sources referred to the DJ equipment vendor as “AlphaCita” — the correct name is AlphaTheta (Pioneer DJ’s parent brand). This article reflects the accurate information.

As always, RC builds are strictly for developers, testers, and hardware validation — they should not be deployed on production systems. Source code is available from Linus Torvalds’s Git tree and as a downloadable tarball from kernel.org.