Linux 7.0 Enters Release Candidate Phase With 14,500 Commits, Intel Nova Lake and AMD Zen 6 Support
Linus Torvalds confirms the next kernel will be 7.0, citing confusion over large numbers, as the first RC ships with one of the largest merge windows on record.
Overview
On February 8, 2026, Linus Torvalds announced that after Linux 6.19 the next kernel release would carry the version number 7.0, marking the first major version increment since the jump from 5.x to 6.0 in 2022. The decision was practical rather than architectural: as Torvalds explained in his announcement, he was “getting to the point where I’m being confused by large numbers (almost running out of fingers and toes again).” Two weeks later, on February 22, 2026, Torvalds tagged the first release candidate, Linux 7.0-rc1, closing a merge window that stands among the busiest the project has ever recorded.
What We Know
The Version Bump Explained
The jump from 6.x to 7.0 does not signal a break in backward compatibility or the arrival of a transformative architectural change. As Torvalds wrote in his announcement, covered by The Register: “We haven’t done releases based on features (or on ‘stable vs unstable’) for a long, long time now. So that new major number does not mean that we have some big new exciting feature, or that we’re somehow leaving old interfaces behind.”
Kernel version history shows this pattern repeating at the end of each minor series. Linux 3.x ended at 3.19, 4.x at 4.20, and 5.x at 5.19. Linux 6.19 now completes the same arc. As reported by Slashdot, the numbering convention serves a practical purpose: keeping the minor version field below a number Torvalds considers unmanageable.
Scale of the Merge Window
The 7.0 merge window closed on February 22, 2026, with approximately 14,500 non-merge commits. According to Tom’s Hardware, roughly two-thirds of the new code addresses drivers, consistent with how the kernel typically grows in proportion to hardware diversity. More than 36 pull requests were queued before the merge window opened.
Hardware Enablement: Intel Nova Lake and AMD Zen 6
The headline additions at the silicon level are early enablement patches for Intel’s upcoming Nova Lake and Diamond Rapids processor generations, alongside AMD Zen 6 support. According to Tom’s Hardware, the Zen 6 perf subsystem now tracks branch prediction, L1 and L2 cache activity, TLB events, and memory controller activity through new hardware performance counters.
Intel TSX is now tuned to auto mode for improved performance on newer Intel CPUs, and DSA 3.0 accelerators are included to offload suitable workloads to dedicated silicon in Xeon deployments. The AMDGPU driver receives display support for Nova Lake’s integrated GPU. Preliminary support for Qualcomm Snapdragon X2 continues its upstream progression.
Beyond x86, Linux 7.0-rc1 adds atomic LS64 and LS64V instructions for ARM64, user-space Control Flow Integrity for RISC-V, and mainline support for the SpacemiT K3 RVA23 SoC — a RISC-V part aimed at embedded and edge workloads. Apple USB Type-C PHY support is also included.
Rust Stabilization Reaches the Driver Core
The 7.0 merge window brings a formal milestone for the Rust-in-Linux effort: Rust support is no longer marked experimental. According to The Register, a patch merged in this cycle cements Rust’s stable status within the kernel, ending its treatment as an optional, unstable feature.
Driver core updates expand what Rust code can do. The changes introduce dev_printk logging across all device types, allow Rust drivers to configure maximum DMA segment sizes via dma_set_max_seg_size(), and add a generic I/O back-end abstraction for device shared memory. A demonstration SoC driver written in Rust accompanies the new SoC device structures as a reference implementation. The revocable synchronization primitive originally planned for 7.0 was reverted for additional refinement before a future cycle.
File System Improvements
The merge window includes updates to Btrfs, XFS, EXT4, F2FS, and exFAT. XFS receives self-healing capabilities. Btrfs gains additional RAID improvements building on the RAID1 read balancing work introduced in 6.14. EXT4, F2FS, and exFAT receive correctness fixes.
Distribution Impact
Linux 7.0 is targeted as the default kernel for Ubuntu 26.04 LTS and Fedora 44, both scheduled for release in spring 2026, according to Tom’s Hardware. Ubuntu 26.04 LTS would be the first long-term support release to ship with a major version-7 kernel — a headline number that carries weight in enterprise procurement even when the engineering change is incremental.
Succession Context
In the 7.0-rc1 announcement post, Torvalds made self-deprecating remarks about his own long-term role, a topic that gained formal structure when the Linux kernel community merged its first succession plan — a document called Documentation/process/conclave.rst — into the repository in late January 2026, as covered by The Register. Torvalds signed the commit himself. The plan designates a 72-hour window following any disruption to his involvement for the broader maintainer community to convene and organize a transition, drawing from participants at the most recent Maintainers Summit and the Linux Foundation’s Technical Advisory Board.
What We Don’t Know
- The exact number of release candidates before the stable release; mid-April 2026 is the projected window assuming a seven-to-eight RC cycle
- Whether the Nova Lake and Zen 6 enablement patches are complete or represent partial early bring-up that will continue in 7.1
- When the Rust Nova GPU driver for NVIDIA hardware — which began its upstream journey in 6.19 — will reach a state suitable for end users
- How the cgroup sub-scheduler feature (sched-ext integration), which missed the 7.0 merge window, will perform in the 7.1 cycle
Analysis
The Linux 7.0 release encapsulates several converging trends in the kernel’s development. The version number change is cosmetic, but it arrives at a moment when the project’s growth indicators are notable: 14,500 commits in a single merge window, first-generation silicon enablement for two major processor architectures, and the formal stabilization of Rust as a first-class kernel language.
Rust stabilization is arguably the most consequential technical development in the 7.0 cycle. After years of internal debate over whether Rust belonged in the kernel at all, the language now occupies a stable, documented position with expanding API surface in driver core. The trajectory from infrastructure scaffolding toward production-quality subsystem implementations is becoming visible in each successive cycle.
The succession document, signed by Torvalds himself, reflects a maturing project confronting realistic questions about long-term stewardship. That the community chose to formalize this process before any crisis — and that Torvalds actively participated — suggests a project that has outgrown dependence on any single point of failure, even as it retains the personality of the person who created it 35 years ago.