Which Liux Distributions Actually Ship Linux 7.0?

Linux 7.0 dropped on April 12, 2026 — but “Linux 7.0 is out” and “your distro ships Linux 7.0” are two very different things. Rolling releases picked it up immediately; major stable distros are on different timelines; and at least one widely-shared claim about Fedora 44 is simply wrong. Here’s a clear, verified breakdown.

First: What Is Linux 7.0, in Brief?

The jump from 6.19 to 7.0 is a numbering convention, not a signal of revolutionary change. Linus Torvalds has long preferred to roll the major version number once the minor count grows unwieldy. “The last week of the release continued the same ‘lots of small fixes’ trend,” he wrote in the release notes, “but it all really does seem pretty benign, so I’ve tagged the final 7.0 and pushed it out.”

That said, 7.0 delivers real milestones: Rust is officially stable in the kernel for the first time, the scheduler receives meaningful fixes for long-standing latency issues, XFS gains self-healing capability, and memory management is measurably faster. AI tooling is also changing how bugs get reported — Torvalds flagged this as potentially the “new normal.” These features matter when choosing whether to upgrade, and are covered in detail further below.

Which Distributions Actually Ship Linux 7.0?

Should You Upgrade — And How?

For users on rolling-release distributions — Arch, Tumbleweed, Gentoo, NixOS unstable — the upgrade is available now. A standard system update is all that’s needed on Arch (sudo pacman -Syu) and Tumbleweed (zypper dup). Gentoo users can pull 7.0 via Portage and should enable the Rust USE flag to take advantage of the newly stable Rust integration. NixOS unstable users can switch via nixos-rebuild switch, with the added safety of atomic rollback if something goes wrong.

For Ubuntu users, 26.04 LTS ships with 7.0 by default from release day. Existing 25.x users should wait for the official LTS upgrade path rather than pulling mainline manually — Canonical’s packaging includes Ubuntu-specific drivers and patches not present in the upstream tarball.

For Fedora users, the picture is clear: Fedora 44 ships 6.19. Fedora Rawhide gives you 7.0 today, but it’s a development branch — not for production. Fedora 45 in October is the stable path. As always, testing in a non-production environment first is wise, regardless of distro.

What’s New in Linux 7.0

For those deciding whether the upgrade is worth it, here’s what 7.0 actually delivers.

Rust Is Now Officially Stable

For more than five years, Rust’s presence in the Linux kernel carried an asterisk. Developers could write Rust modules, but the language was explicitly labelled experimental — subject to API churn, incomplete toolchain support, and uncertain long-term commitment from the kernel community.

That asterisk is gone in 7.0. The decision was made at the Linux Kernel Maintainers Summit held in late 2025, where developers reached consensus that Rust had proven itself in production contexts and the experimental label should be formally retired.

In practical terms, the kernel build system now treats Rust modules as first-class citizens. The Rust kernel API has grown to cover PCI device enumeration, interrupt handling, DMA mapping, and platform device registration — the foundational building blocks needed to write real hardware drivers. Cross-compilation targeting x86_64, ARM64, and RISC-V is fully supported.

Rust’s memory safety model — which eliminates entire categories of bugs like buffer overflows and use-after-free errors at compile time — has long made it an attractive complement to the kernel’s predominantly C codebase. With stable status now conferred, distro teams and driver authors can commit to Rust-based code without fear that upstream APIs will shift under them.

The ‘Rust experiment’ has been concluded. Rust is here to stay.

— 9to5Linux, summarising the kernel community consensus

Scheduler and Performance Improvements

Linux 7.0 fixes a long-standing scheduler problem: previously, the CPU could pull a thread off the processor mid-task — even during a critical section — causing micro-stutter and latency spikes under heavy workloads. That behaviour is addressed in 7.0, with improvements that benefit both desktop responsiveness and server throughput.

Memory management received a significant overhaul as well. Allocation time for large memory blocks dropped substantially, and continued work on the swap subsystem delivers measurable throughput improvements under memory pressure. Thread creation and teardown is 10–16% faster thanks to PID allocation improvements, and file open/close operations are 4–16% quicker on multi-core machines under benchmark conditions.

Container workloads benefit from a new OPEN_TREE_NAMESPACE option in open_tree(), which allows container runtimes to create a new mount namespace without cloning an entire existing one — reducing container creation overhead significantly in testing.

Filesystem Highlights

XFS gains autonomous self-healing support in 7.0, allowing the filesystem to detect and repair metadata corruption at runtime without requiring an unmount. This is a particularly meaningful addition for long-running servers where taking a volume offline for repair is disruptive.

EXT4 receives improved write performance for concurrent direct I/O across multiple files. Btrfs gains support for direct I/O when block size exceeds page size, along with early support for a remap-tree feature. A new standardised I/O error reporting API replaces a long-standing inconsistency in how block-layer errors bubble up to userspace.

Security Changes

On the security front, 7.0 adds ML-DSA post-quantum signatures for kernel module authentication — a forward-looking change as quantum computing threats to classical cryptography grow more concrete. In the same sweep, support for SHA-1-based module signing schemes has been removed.

BPF filtering for io_uring arrives in this release, giving administrators a way to sandbox io_uring operations in restricted environments. This closes a gap that had previously led some operators to disable io_uring altogether as a blunt-force security measure.

AI’s Growing Role in Kernel Development

One of the more culturally significant aspects of the 7.0 release is what Torvalds said about the development process itself. In his release notes, he observed that AI-assisted tooling appears to be surfacing edge cases that might otherwise go undetected — and suggested this may become the “new normal” for kernel development.

Stable kernel maintainer Greg Kroah-Hartman echoed that assessment, noting that the AI-assisted bug reports coming in have been substantively useful rather than low-quality noise. The 7.0 cycle also formalised documentation — including guidance specifically aimed at AI coding assistants — on how contributors should use development tools responsibly.

I suspect it’s a lot of AI tool use that will keep finding corner cases for us for a while, so this may be the “new normal” at least for a while. Only time will tell.

— Linus Torvalds, Linux 7.0 release announcement

Hardware Support Highlights

Beyond the headline features, 7.0 includes a broad sweep of hardware enablement work. Intel’s upcoming Nova Lake and Crescent Island platforms receive continued bring-up. AMD Zen 6 performance events and metrics support is added. The open-source NVK driver for newer Nvidia GPUs gains improved performance via restored large page support. Old AMD GCN 1.0 and GCN 1.1 Radeon GPUs — which gained native Vulkan support in 6.19 via the amdgpu driver — receive further stability fixes in 7.0.

Intel TSX (Transactional Synchronization Extensions) now defaults to “auto” mode on capable CPUs without known security issues, which should improve out-of-the-box performance on recent Intel hardware without manual tuning. On the more whimsical end of the changelog, Bluetooth support for Rock Band 4 guitars on PS4 and PS5 is now included in the mainline kernel.

Sources: Phoronix, 9to5Linux, The Register, OMG! Ubuntu, StorageNewsletter, Wikipedia Linux kernel version history, Fedora Discussion forums. All distribution support statuses reflect information available as of April 21, 2026.