Quick take: Linus Torvalds tagged Linux kernel 7.2-rc1 on June 29, 2026, closing the two-week merge window for the 7.2 development cycle. RC1 lands new GPU, Wi-Fi, and storage drivers, scheduler improvements for heterogeneous CPU topologies, expanded Rust driver contributions, and a crop of security fixes across the netfilter, io_uring, and memory management subsystems.
Introduction
Linus Torvalds announced the first release candidate for Linux kernel 7.2 on the Linux Kernel Mailing List (LKML) on June 29, 2026. The announcement follows the standard two-week merge window that opened immediately after Linux 7.1 reached stable, during which maintainers submit new features, driver additions, and subsystem updates through Linus's tree.
In his LKML post, Torvalds described the release as "fairly normal sized" with no single dominant area of change, which is typically a good sign for RC1 stability. The cycle kicked off with approximately 13,000 non-merge commits touching around 1,600 files — a typical merge window volume for the 7.x series. Most of the new code comes from driver subsystems, followed by architecture-specific updates and networking.
What Is a Release Candidate?
Linux kernel release candidates (RCs) mark the point at which the merge window closes and the focus shifts from adding features to fixing bugs. RC1 is always the least stable release in any kernel cycle because it's the first point at which all new code from the merge window is assembled together and tested as a whole. New regressions introduced during the merge window tend to surface during the RC phase.
The process works like this: Linus releases RC1, then RC2, RC3, and so on approximately every week. Each subsequent RC contains regression fixes, stability improvements, and documentation updates — but no new features. By the time RC6 or RC7 arrives, most regressions are resolved, and the kernel is considered stable enough for a final release.
Key Changes in Linux 7.2 RC1
Based on the merge window activity tracked on LKML and in subsystem pull requests, the following areas see the most significant changes in Linux 7.2:
- Scheduler: Improvements to the Energy-Aware Scheduling (EAS) layer for better task placement on asymmetric CPU topologies — primarily benefiting ARM big.LITTLE and x86 hybrid processors (Intel's P/E-core designs). Latency improvements for interactive workloads were also merged.
- Rust drivers: Additional Rust-language driver contributions landed in 7.2, continuing the incremental expansion of Rust in the kernel. New Rust abstractions for PCI and platform bus devices are included.
- Memory management: Improvements to the multi-gen LRU (MGLRU) page reclaim algorithm, reducing memory pressure on workloads with large working sets. Several fixes to transparent huge pages (THP) handling also landed.
- io_uring: Continued work on io_uring ring-mapped buffers and zero-copy networking integration. Several security fixes addressing potential privilege escalation paths were also merged.
Driver and Hardware Support Updates
Driver changes make up the bulk of any kernel merge window, and Linux 7.2 is no exception:
- GPU / DRM: Updated amdgpu driver adding support for newer RDNA 4 variants. Intel i915 and xe drivers gain better power management on Meteor Lake and Lunar Lake platforms. Nouveau (open-source NVIDIA driver) continues incremental improvements for Turing and Ampere.
- Wireless: The ath12k driver (Qualcomm Wi-Fi 7 chipsets) receives improved multi-link operation (MLO) support. The iwlwifi driver gains firmware support for newer Intel BE200 and BE202 adapters.
- NVMe and storage: NVMe-oF TCP sees performance improvements under high queue depth workloads. The bcachefs filesystem receives several stability fixes after its integration in the 6.7 cycle.
- USB: New USB4 v2 (80 Gbps) controller driver contributions. Updated xhci driver with improved Thunderbolt 5 link speed negotiation.
Networking and Storage Changes
The networking subsystem sees a focused set of changes in 7.2 rather than a wholesale overhaul. Key items include XDP (eXpress Data Path) performance improvements for multi-core scaling, incremental SMC-R (Shared Memory Communications over RDMA) refinements, and several netfilter fixes addressing use-after-free conditions identified during fuzz testing. The virtio-net driver also gains improvements benefiting guest networking throughput in KVM and QEMU virtual machines — relevant for anyone running Linux guests on Proxmox or other KVM-based hypervisors.
On the filesystem side, ext4 receives fixes for delayed allocation edge cases, and XFS lands improvements to online scrub and repair functionality. Btrfs continues its incremental improvement cadence with send/receive performance work and RAID 5/6 journal fixes.
Security and Architecture Improvements
Linux 7.2 RC1 incorporates security improvements across several subsystems. The most notable are:
- io_uring hardening: Tightened validation of ring buffer operations following continued research into io_uring-based privilege escalation techniques.
- Landlock updates: The Landlock security module receives new abstractions for network access control, allowing unprivileged sandboxing of network-facing applications without seccomp filter complexity.
- AARCH64 (ARM64): Page table entry permission improvements for Arm Confidential Compute Architecture (CCA) guest VMs. Updated support for Arm v9.2 memory tagging extensions.
- RISC-V: Improved support for the Sv57 five-level page table extension and hypervisor extension updates.
- x86: Shadow stack (CET-SS) improvements for AMD Zen 4 and Intel Tiger Lake+ processors. Updated Spectre and Retbleed mitigations with reduced overhead paths.
How to Test Linux 7.2 RC1
Testing release candidates helps catch regressions before they reach stable users. To test Linux 7.2 RC1 on a non-production system:
# Clone the mainline kernel tree
git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
# Check out the RC1 tag
git checkout v7.2-rc1
# Copy your current config as a starting point
cp /boot/config-$(uname -r) .config
make olddefconfig
# Build (replace 8 with your CPU core count)
make -j$(nproc)
# Install modules and kernel
sudo make modules_install
sudo make install
# Update GRUB
sudo update-grub
If you encounter a regression — a problem that works on 7.1 but fails on 7.2-rc1 — report it on the Linux Kernel Mailing List with the output of git bisect identifying the offending commit. Kernel developers rely on community regression reports during the RC phase to catch issues before the stable release.
Expected Release Timeline
Based on historical Linux kernel release cadence, Linux 7.2 is expected to follow this approximate schedule:
- 7.2-rc1: June 29, 2026 (released)
- 7.2-rc2: July 6, 2026
- 7.2-rc3: July 13, 2026
- 7.2-rc4: July 20, 2026
- 7.2-rc5: July 27, 2026
- 7.2-rc6: August 3, 2026
- 7.2-rc7 (if needed): August 10, 2026
- 7.2 stable: August 10–17, 2026
These dates are projections. If significant regressions emerge during testing, Linus may add extra RC rounds and push the stable release by one to two weeks.
Final Thoughts
Linux 7.2's merge window reflects the ongoing maturation of the 7.x series: incremental but meaningful improvements across drivers, the scheduler, memory management, and security, rather than a single headline-grabbing architectural change. The expansion of Rust driver contributions in 7.2 is the most strategically significant trend to track — the language is steadily expanding its footprint in kernel subsystems and will become an increasingly normal part of driver development over the next few major releases.
For system administrators, the actionable takeaway from 7.2 RC1 is to watch for the stable release in August and assess scheduler and NVMe improvements for workloads on heterogeneous CPU platforms and high-throughput storage systems. Distributions like Fedora and Arch will pick up 7.2 quickly; RHEL and Ubuntu LTS users will receive backported fixes through their vendor kernels over a longer horizon.
FAQ: Linux Kernel 7.2 RC1
What changed between Linux kernel 7.1 and 7.2?+
Linux 7.2 brings new wireless and storage driver support, scheduler latency improvements targeting workloads on heterogeneous CPU topologies, updated GPU and media subsystem drivers including expanded Rust driver contributions, refreshed ARM and RISC-V architecture code, and multiple security fixes across the netfilter, io_uring, and memory subsystems. See the key changes section above for a full breakdown.
When will Linux kernel 7.2 be officially released as stable?+
Following the standard Linux kernel release cadence, Linux 7.2 is expected to go stable approximately seven to eight weeks after the RC1 tag on June 29, 2026. The projected stable release window is mid- to late August 2026, subject to the number of release candidates needed to resolve any regressions.
Is Linux 7.2 RC1 safe to run in production?+
No. Release candidates are strictly for testing and development environments. RC1 is the least stable point in the release cycle — all new merge-window code has just landed but broad regression testing has not yet occurred. Run RC kernels only on dedicated test machines or non-critical development systems, never on production servers or desktops that handle important workloads.
How can I compile and install Linux 7.2 RC1 from source?+
Clone the mainline tree with git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git, check out v7.2-rc1, copy your current config with cp /boot/config-$(uname -r) .config, run make olddefconfig, then build with make -j$(nproc). Install with sudo make modules_install && sudo make install, update GRUB, and reboot.
Which Linux distributions will ship Linux kernel 7.2 by default?+
Fedora and openSUSE Tumbleweed typically track upstream releases closely and are likely to ship Linux 7.2 within weeks of the stable release. Arch Linux and Manjaro will pick it up shortly after the stable tag. Ubuntu will include it in upcoming interim releases. LTS distributions like RHEL and Ubuntu LTS ship backported kernels and may not adopt 7.2 natively for a year or more.
Need help with infrastructure or virtualization?
Work directly with Muhammad Irfan Aslam for Linux, Proxmox, Docker, DevOps, cloud, CI/CD, or infrastructure support.
Hire Me for Support