Linux kernel releases follow a rhythm. Every few months, a new branch lands, lives for a short window, then goes quiet. Most users never notice this rhythm because their distro handles it for them. The folks who notice are the ones who compiled a bleeding-edge kernel by hand six months ago and forgot about it.
That is the situation for anyone running Linux 7.1 today. Greg Kroah-Hartman published 7.1.13 on September 2, 2026, and called it plainly. The 7.1.y series is end of life. Please move to the 7.2.y series at this point in time. 7.1.13 is the final patch you will see on that branch.
If you do not run uname -r today, you might be running a kernel that will not get another security fix.
What 7.1 actually did for you
The 7.1 branch came out on June 14, 2026, and it had one feature that justified the entire release cycle for most users. The NTFS driver got a complete rewrite that had been in development for about four years. The old ntfs3 driver could read NTFS partitions from Windows machines but only had experimental write support that would lose data if you pushed it. The new driver in 7.1 finally gave you a normal write experience on those partitions, with a fresh userspace toolset (ntfsprogs-plus) to go with it.
If you have ever plugged a Windows-formatted external drive into Linux and been told it was read-only, that was the old driver. With 7.1, that workflow stopped being a problem.
There were other improvements, of course. The AMDGPU driver gained initial HDMI 2.1 FRL support, which matters if you have one of the newer high-refresh monitors and have been dealing with detection issues. The Intel Xe driver picked up initial CRI platform support. A new “Fair(er)” GPU scheduler aimed to make mixed workloads feel less jerky. None of those were small. None of them were the headline. The headline was NTFS.
Why short-lived branches die on schedule
The Linux kernel project publishes two kinds of releases. The stable branches come out every two or three months, get a handful of patch releases, and then go quiet. The LTS branches (Long Term Support, the project designation for kernel versions that receive security backports for years instead of weeks) come out of the same merge window but get backported for two to six years. The 7.1 branch was a normal stable release. It was never supposed to be long term. The release notes said so when it shipped.
That sounds wasteful if you only upgrade once a year. It is actually how new hardware support, filesystem work, and driver rewrites land without waiting two years for the next LTS roll-around. The trade is that you have to move when the branch moves. You cannot camp on 7.1.13 and expect it to keep working.
The branches that are still receiving backports as of September 2026:
- 6.18 LTS, supported through late 2027
- 6.12 LTS, supported through late 2027
- 6.6 LTS, supported through late 2027
- 6.1 LTS, supported through late 2028
For most desktop and server users, picking whichever one of these your distro already tracks is the right answer. Stable distro vendors like Ubuntu, Fedora, Debian, and openSUSE Leap already map their kernel updates to one of these branches. You do not need to do anything special. You need to make sure you are not on 7.1 by accident.
How to read your version number
Open a terminal. Run uname -r. The output tells you exactly where you stand.
- 7.1.x means you are on the branch that just died. Plan an upgrade this week.
- 7.2.x means you are on the next short-lived branch, which will probably follow 7.1 into retirement in a couple of months. Plan an upgrade for late 2026.
- 6.18.x, 6.12.x, 6.6.x, or 6.1.x means you are on an LTS branch with a year or more of runway. You can stop reading.
- Anything older than 6.1 means you are on a branch that may or may not still be receiving backports. Check kernel.org before you assume you are safe.
Most users will land in the third bucket. Most of the rest will land in the first bucket because they followed a tutorial six months ago that told them to install a mainline kernel for some specific hardware reason. The second and fourth buckets are rare.
What the upgrade actually involves
For rolling-release distro users, the upgrade is invisible. Arch, openSUSE Tumbleweed, and the like have already shipped 7.2 in their normal package flow. A normal pacman or zypper update brings it in. You do not need to do anything beyond running the update and rebooting.
For stable distro users, the upgrade path depends on the distro. Some distros move between LTS branches with each major release, others track a single LTS branch and backport security patches to it. Your distro’s release notes or wiki will tell you which path you are on. Most of the time, the kernel update is part of the normal package update flow and does not need separate intervention.
The path that gets people in trouble is the one where they hand-installed a kernel from kernel.org for hardware reasons and then forgot about it. If that is you, the upgrade path depends on what your distro ships. Most of the time, you can just remove the hand-installed kernel and let the distro take over. A few times, you have to switch to a newer hand-installed kernel because the hardware you needed it for is not yet supported in the distro default.
What you should not do
Three things to avoid:
- Do not stay on 7.1.13 and hope someone publishes 7.1.14 next month. That is not how short-lived kernel branches work. You will not get the fix.
- Do not compile a fresh kernel from kernel.org without a specific hardware reason. The cost is high and the benefit for most users is zero.
- Do not skip the kernel update on a server because the rest of the upgrade is too much work. Kernel-only security backports are usually a small subset of the full upgrade.
Trade-offs
The trade-off with the kernel release cadence is that “stable distro” means “stable kernel branch” only if your distro actually maps to one of the LTS tracks. Most do. A few ship short-lived branches by default, which means you need to opt into the LTS path yourself. If you are not sure which track your distro follows, the wiki for your distro will tell you. The kernel.org LTS page is the ground truth for which branches are still receiving backports.
The other trade-off is that the LTS branches are not free in terms of features. You will not get the NTFS rewrite, the new AMDGPU HDMI support, or the Fair(er) GPU scheduler unless you move to 7.2 or wait for those features to be backported. For most desktop users, that wait is fine. For a workstation with newer hardware that needs the latest drivers, it is not fine, and the right answer is to track the short-lived branches deliberately.
If you are running a server, the answer is almost always an LTS branch on a stable distro. The cost of a kernel bug on a server is higher than the cost of missing out on a new feature. If you are running a desktop and your hardware is more than two years old, the LTS answer is also right. If you are running bleeding-edge hardware on a desktop, you might need to track 7.2 or even mainline, and that is a deliberate choice you should make with eyes open.
Bottom line
Run uname -r. If it shows 7.1.x, schedule a kernel upgrade this week. If it shows 7.2.x, schedule one for late 2026. If it shows an LTS version, you are fine. The kernel team does not expect you to chase the latest branch. They expect you to know which branch you are on and move off the ones that just stopped getting patches.
The end of a short-lived kernel branch is not a crisis. It is the rhythm. Pay attention for ten minutes, move on with your week.