Linux 7.2-rc7 became available on 9 August 2026, moving the next Linux kernel another step closer to its stable release. The new build is a release candidate, so it is intended for testing rather than everyday use on an important computer.
If no major regression requires an RC8 build, Linux 7.2 could reach stable as soon as 16 August 2026. This is an estimate, not a confirmed release date.
For most desktop and server users, there is nothing to install today. The practical news is that testing has reached a late stage, while distribution maintainers and hardware developers get another opportunity to find regressions before Linux 7.2 is declared stable.
- Linux 7.2-rc7 was published on 9 August and remains a pre-release kernel.
- Developers and experienced testers can use it to check hardware and software compatibility.
- Regular users should continue using the kernel supplied and supported by their Linux distribution.
Linux 7.2-rc7 is now available
The official kernel.org release page lists Linux 7.2-rc7 as the current mainline build, dated 9 August 2026. On the same day, maintainers also published Linux 7.1.8 and updates for several long-term support branches.
The “mainline” label is important. It refers to the kernel version currently being developed by Linus Torvalds and contributors. It is different from the stable and long-term branches that most distributions use for production systems.
| Kernel branch | Status on 9 August | Best suited for |
|---|---|---|
| Linux 7.2-rc7 | Mainline pre-release | Testing and development |
| Linux 7.1.8 | Stable update | Distribution maintainers and supported deployments |
| Linux 6.18, 6.12 and older LTS branches | Long-term maintenance | Systems that value a longer support window |
What does RC7 actually mean?
“RC” means release candidate. After a kernel merge window closes, new development moves through a series of weekly candidates. Maintainers use this period to fix regressions, review late problems and make the code safer for a stable release.
The number seven means this is the seventh candidate in the Linux 7.2 testing cycle. It does not promise that the next build will be stable. If an important regression appears, another release candidate can be published before the final version.
The Linux Kernel Organization explains that prepatch or RC kernels are mainly meant for developers and Linux enthusiasts. Its release documentation also describes the normal mainline cycle as roughly nine to ten weeks, although the actual schedule depends on the condition of the code.
That makes RC7 a sign of progress, not a deadline. Linux 7.2 is close enough for distributions and hardware vendors to test seriously, but the final decision still belongs to the upstream maintainers.
What is new in Linux 7.2?
Linux 7.2 includes more than final-stage fixes. The release cycle brings cache-aware scheduler work, fairer GPU job scheduling, improvements to memory reclaim and swapping, faster Btrfs operations, USB4 data-stream support and a new inline block-encryption target. These changes will matter differently depending on the hardware and workload, so users should wait for distribution testing before expecting a guaranteed performance improvement.
The KernelNewbies Linux 7.2 changelog provides a technical overview and links to deeper coverage of the individual changes.
Who should test Linux 7.2-rc7?
Experienced users may want to test RC7 when they have recently released hardware, maintain a kernel driver, package software for a distribution or need to confirm that an earlier regression has been fixed.
A useful test is more than booting the computer once. Testers should check suspend and resume, networking, graphics, sound, storage devices, virtual machines and any workload that matters on that machine. They should also keep an older working kernel in the boot menu.
Testing is especially valuable when a bug report contains clear hardware information, logs and steps that another developer can reproduce. A simple statement such as “the new kernel is broken” rarely provides enough information to identify the cause.
Use a spare machine or virtual machine
The safest place to explore a release candidate is a test computer or a virtual machine. Even then, make a backup and confirm that you know how to boot the previous kernel. Administrators using Plesk can follow our remote Plesk backup guide for an additional off-server copy. Secure Boot, proprietary graphics modules and out-of-tree drivers may require extra attention.
Running a mainline kernel can also move a system outside the normal support path offered by its distribution. If something fails, the distribution may ask you to reproduce the problem using its officially packaged kernel.
What should regular Linux users do?
Most people should wait. Ubuntu, Fedora, Debian, Linux Mint, openSUSE and other distributions test kernels with their own packages, patches and upgrade tools. Installing the supported distribution update is normally safer than downloading a mainline build manually.
A new kernel number does not automatically make an existing system faster. The result depends on the processor, graphics hardware, storage, drivers and workload. A stable system with a supported kernel is usually more valuable than a newer number with an unknown regression.
Server administrators should be even more careful. Before any kernel upgrade, check application compatibility, monitoring, backup recovery and the ability to return to the previous kernel. Our Linux server hardening checklist covers related protections that should remain in place during maintenance. Availability matters more than joining the first day of a new release.
Where could Linux 7.2 appear?
Canonical has already announced that Linux 7.2 is the target kernel for Ubuntu 26.10 “Stonking Stingray”. That does not mean Ubuntu users should install RC7 manually. It means Ubuntu’s kernel team is preparing its development work around this upstream series.
Rolling-release distributions may package the stable kernel sooner, while fixed-release distributions can wait for additional testing or a later point update. Each project has its own schedule, patch set and support policy.
Ubuntu 26.04 LTS users should continue following the supported LTS update path. The appearance of Linux 7.2 upstream does not change the kernel support promise attached to an installed Ubuntu LTS system.
What happens next?
For the stable release date, distribution availability and future milestones, follow our continuously updated Linux 7.2 Release Tracker.
Upstream developers will continue reviewing fixes and regression reports. If the remaining problems are small and the release looks ready, Linux 7.2 can move to stable. If not, the cycle can continue with another candidate.
After the stable release, distribution maintainers decide when and how to package it. Users should read their distribution’s announcement rather than treating the upstream release as a universal upgrade instruction.
Linux 7.2-rc7 is therefore encouraging news for the development cycle, but it is not an emergency update. Testers have something useful to examine today; everyone else can wait for the stable kernel and a supported package from their distribution.
Primary sources
- The Linux Kernel Archives: current mainline and stable releases
- Linux Kernel Organization: active kernel releases and RC terminology
- Canonical Kernel Team: Linux 7.2 target for Ubuntu 26.10
Published: 10 August 2026. We will update this article when Linux 7.2 reaches its stable release.
Comments