Linux Kernel 7.1.8 (End of Life)

End of life: the 7.1 series was a regular stable branch, not a longterm one, and it reached end of life with 7.1.13 on September 2, 2026. It no longer receives fixes. Move to Linux 7.2.8 or a longterm branch such as 6.18.54.

Linux 7.1.8 shipped on August 19 as part of a batch of four stable releases pushed by Greg Kroah-Hartman and Sasha Levin, alongside 6.18.44, 6.12.103, and 6.6.151.

The AMDGPU brightness fix

The reason to care about this specific release is a brightness control regression that affected 7.1.6 and 7.1.7 on AMD graphics. If you are on an AMD laptop running either of those versions and your brightness keys stopped working, this is the fix rather than a hardware fault.

Regressions inside a stable series are the awkward case, because the entire premise of a stable branch is that updates are safe to take without thinking. A brightness bug shipping in two consecutive point releases is exactly the sort of thing that teaches people to defer updates, which is the opposite of what you want. It was caught and fixed quickly.

AerynOS moved its stable and gaming kernels to 7.1.8 for this reason.

What a stable point release contains

Stable releases carry no new features. They are backports of fixes that already landed in mainline, tested against the linux-stable testing tree, and applied only after they have been in circulation for a while. The release announcement text is the same every time for a reason:

This is a stable release containing fixes for regressions and other issues. These fixes have been tested against the linux-stable testing tree and have been applied for some time. We encourage all users to review and test this new stable kernel.

This batch carries hundreds of fixes across the block layer, the networking stack, and the major filesystems.

Building it

tar xf linux-7.1.8.tar.xz
cd linux-7.1.8
cp /boot/config-$(uname -r) .config
make olddefconfig
make -j$(nproc)
sudo make modules_install install

Most people should not do this. Your distribution ships these kernels through its normal update channel, already configured, signed, and integrated with your bootloader. Building from source is for developers, for bisecting a regression, or for enabling something your distribution does not.

# The usual route
sudo apt update && sudo apt full-upgrade   # Debian and Ubuntu
sudo dnf upgrade --refresh                 # Fedora
sudo pacman -Syu                           # Arch

A kernel update does not take effect until you reboot, and uname -r reports the running kernel rather than the newest installed one.

On the CVE numbers

If the volume of security fixes in a stable release looks alarming, it is worth understanding why. The kernel became its own CNA in 2024 and now assigns CVEs to essentially every fix that could conceivably carry a security implication, which produces very large CVE counts that do not map to proportionally large risk. We covered that in why the kernel published 432 CVEs in two days.

The practical guidance: track a stable branch, take its updates, and do not attempt to triage individual kernel CVEs unless that is specifically your job.

Verify Your Download

Every tarball on kernel.org is signed. Verify before building:

curl -O https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.1.8.tar.sign
unxz linux-7.1.8.tar.xz
gpg --verify linux-7.1.8.tar.sign