Linux 7.2-rc6 is out, and Linus Torvalds flagged it as an unusually large release candidate for this late in the cycle, driven by another heavy round of bug fixing rather than new feature work. With rc6 in testing, a stable Linux 7.2 release is on track for around August 16, 2026, following the kernel’s usual pattern of tapering rc sizes as a cycle approaches final.

What shipped in the 7.2 merge window

The merge window closed with 7.2-rc1 back on June 28, and the feature set has held steady through the rc cycle since. The headline addition is Cache Aware Scheduling (CAS), a CPU scheduler change that tracks which cache a task’s working set was last resident in and biases future placement toward keeping it there, aimed at reducing the cost of migrating tasks between cores on multi-core and multi-socket systems.

The cycle also completes a six-year effort to remove the deprecated strncpy() API from the kernel tree in favor of safer alternatives like strscpy(), and enables large folios by default on Btrfs, reducing per-page bookkeeping overhead on large file operations such as backups and media library scans. On the driver side, 7.2 picks up initial AMD ISP4 image signal processor support, early AMDGPU HDMI 2.1 Fixed Rate Link support, and Intel Xe driver work for newer platform and CPU model coverage.

What rc6 is fixing

Release candidates this late in a cycle are almost entirely regression fixes and driver stabilization rather than new functionality. The size of rc6 suggests the merge window pulled in more churn than usual for a cycle this far along, which is consistent with a feature set that includes a scheduler change (CAS) and a large filesystem behavior change (Btrfs large folios), both categories of change that tend to surface edge cases only under real-world testing at scale.

# Check your currently running kernel
uname -r

# Arch users tracking rc kernels via testing repos
pacman -Qi linux-rc 2>/dev/null

# Build from source if you want to test 7.2-rc6 directly
# tarball and signed changelog are available at kernel.org

What to expect before final

Expect at least one more release candidate before Linus tags stable 7.2, and possibly two if rc6’s fix volume does not taper off quickly. Distribution kernel and testing teams for Arch, Gentoo, and Fedora’s Rawhide typically package rc kernels within a few days of each tag for users who want to test ahead of general availability, though running an rc kernel on a production system is not recommended given the ongoing regression fixes.

Once 7.2 ships as stable, expect the usual overlap: a new 7.1.x point release or two may still land shortly after, backporting any final fixes discovered late in the 7.2 cycle to the outgoing stable branch before it’s superseded.