After more than two decades of incremental version numbering under the Linux 6.x series, Linus Torvalds has once again bumped the major version number of the world’s most widely deployed open-source kernel. Linux 7.0-rc1 has been released, and as with the jump from 5.x to 6.0 in 2022, the creator of the kernel is quick to remind everyone that the change is cosmetic rather than substantive.
The release candidate dropped on February 23, 2026, following the standard two-week merge window that defines each Linux kernel development cycle. As reported by The Register, Torvalds made the decision primarily because the minor version numbers were getting unwieldy. Linux 6.x had reached version 6.14 before the bump, and Torvalds has long maintained that he prefers to reset the counter before numbers climb too high — a quirk of personal preference rather than any engineering milestone.
A Number, Not a Revolution: Why Major Version Bumps Don’t Mean What You Think
For those outside the Linux kernel development community, a jump from version 6 to version 7 might suggest a dramatic overhaul — the kind of generational leap that commercial software companies use to justify new licensing fees or marketing campaigns. In the Linux world, nothing could be further from the truth. Torvalds has been consistent on this point for years. When Linux moved from 5.19 to 6.0 in October 2022, he wrote in his release announcement that the change carried “no particular reason” beyond his discomfort with letting minor version numbers creep past 20, as happened during the long Linux 4.x series that ran from 2015 to 2020.
The same philosophy applies now. According to The Register, Torvalds reiterated in his mailing list post accompanying the 7.0-rc1 tag that there is “nothing special” about the release from a feature perspective. Each kernel release, whether it carries a major version bump or not, follows the same disciplined process: a two-week merge window during which maintainers submit their accumulated patches, followed by roughly seven weeks of release candidates aimed at stabilizing the code before the final release.
What Actually Shipped in the Merge Window
While the version number itself may be arbitrary, the contents of the 7.0 merge window are not. The release includes a substantial set of changes across multiple subsystems, consistent with the pace of modern kernel development. Each merge window typically incorporates between 12,000 and 16,000 commits from thousands of developers worldwide, and the 7.0 cycle appears to be no exception.
Among the notable changes reported by The Register are continued improvements to the Rust-for-Linux initiative, which has been gradually expanding the use of the Rust programming language within the kernel since its initial inclusion in Linux 6.1 in late 2022. The 7.0 merge window brought additional Rust abstractions for kernel subsystems, moving the effort closer to the point where real device drivers written in Rust can ship as part of the mainline kernel. This has been one of the most closely watched developments in kernel engineering, as Rust’s memory safety guarantees could significantly reduce the class of bugs that account for a large share of kernel vulnerabilities.
Hardware Support and Architecture Updates
As with every kernel release, hardware enablement remains a major focus. The 7.0 merge window included updates for recent AMD and Intel processor generations, with power management and performance tuning patches that matter enormously to data center operators and cloud providers who run Linux on millions of servers. ARM64 architecture support also received attention, reflecting the growing importance of Arm-based chips in both server and embedded applications — a trend accelerated by the success of chips like AWS Graviton and Ampere Altra in hyperscale environments.
Filesystem work continues as well. Bcachefs, the copy-on-write filesystem that entered the kernel in Linux 6.7, received further stabilization patches. Its developer, Kent Overstreet, has been working to bring the filesystem to production readiness, and each kernel cycle brings it closer to being a viable alternative to established options like ext4, XFS, and Btrfs. The 7.0 cycle also included ongoing work on io_uring, the asynchronous I/O interface that has become central to high-performance Linux applications.
The Cadence That Keeps the World Running
One of the most remarkable aspects of Linux kernel development is its metronome-like regularity. Since adopting the time-based release model in 2005 after the transition to Git, the kernel has shipped a new release approximately every nine to ten weeks without fail. This cadence has held through economic downturns, global pandemics, and the explosive growth of cloud computing. The process is maintained by a hierarchy of subsystem maintainers who funnel patches upward to Torvalds, who acts as the final integrator.
This reliability is part of what makes the version number question so interesting from an organizational standpoint. In most software projects, version numbers carry semantic meaning — a major version bump signals breaking changes or significant new capabilities. The Linux kernel explicitly rejects this convention. Every release is expected to maintain backward compatibility with userspace applications, a commitment Torvalds has described as one of the kernel’s most important rules. Breaking userspace is, in his words, “the one rule” that cannot be violated, regardless of what the version number says.
Enterprise Implications: What Distributions Will Do With 7.0
For enterprise Linux users, the raw kernel version number matters less than which kernel their distribution vendor chooses to base its next long-term support release on. Red Hat Enterprise Linux, SUSE Linux Enterprise, and Ubuntu LTS releases each select a specific kernel version and then backport security fixes and selected features for years or even decades. Canonical’s Ubuntu 26.04 LTS, expected in April 2026, could potentially ship with a kernel based on the 7.0 series, though the timing will depend on how the release candidate cycle progresses.
Distribution vendors have become sophisticated at decoupling their support timelines from upstream kernel releases. Red Hat, for instance, has historically maintained kernels for ten or more years, backporting thousands of patches while keeping the same base version number. This means that many enterprise servers are running kernels that are nominally years old but contain modern security and hardware support. The shift to 7.0 upstream will eventually filter down to these distributions, but on their own schedules.
The Rust Question Looms Larger With Each Release
Perhaps the most consequential long-term story in kernel development is the expanding role of Rust. When Rust support was first merged in Linux 6.1, skeptics questioned whether the language would gain meaningful traction in a project dominated by C for over three decades. Three years later, the momentum is undeniable. Each merge window has brought new Rust infrastructure, and the 7.0 cycle continued that trend. The question is no longer whether Rust will be used in the kernel but how quickly it will spread beyond infrastructure code into actual drivers and subsystems.
This matters because the Linux kernel is one of the most security-critical pieces of software on Earth. It runs on everything from Android phones to the servers powering global financial markets. Memory safety bugs in C code — buffer overflows, use-after-free errors, and similar issues — have historically been responsible for a significant percentage of kernel vulnerabilities. Google’s Android security team and Microsoft’s security researchers have both published data suggesting that roughly 70% of serious vulnerabilities in large C and C++ codebases stem from memory safety issues. Rust’s ownership model eliminates entire categories of these bugs at compile time.
What Comes Next: The Road to 7.0 Final
Following the standard kernel development process, Linux 7.0-rc1 will be followed by weekly release candidates — typically seven or eight — before the final 7.0 release, expected sometime in April 2026. During this period, no new features are accepted; the focus shifts entirely to bug fixes and regression hunting. Torvalds has been known to extend the release candidate phase if significant regressions are discovered, though this is relatively rare.
The kernel community will then immediately open the merge window for Linux 7.1, and the cycle begins again. This relentless pace of development — roughly six major releases per year — is what allows Linux to keep up with the rapid evolution of hardware and the demands of its vast user base. Whether the version number reads 6.15 or 7.0, the machinery underneath keeps turning with the same discipline it has maintained for two decades. For Torvalds, that consistency matters far more than any number.