Stable kernel releases for Friday with a single bug fix

The Linux maintainers have issued a coordinated set of stable kernel updates across five major series. Each update carries a single corrective change that addresses a regression discovered after the security patches for CVE-2026-68480 were applied. The regression was identified by Thomas Lamprecht and was present in the kernels released just a day earlier. By backporting the original security fix and adding the bug correction, the new kernels aim to re-establish the intended protection against speculative-execution data leakage.

The bug in question manifested only in the kernels that incorporated the yesterday’s security fix, meaning systems that remained on older, unpatched kernels were not directly affected. However, those that upgraded to the immediate security releases now face a functional issue that could undermine stability or performance. For engineers, this creates a narrow window where the security patch is present but a new bug compromises its reliability, necessitating a prompt follow-up update.

Deploying the new stable kernels involves the usual upgrade path: installing the updated packages and rebooting into the new kernel version. The operational cost is limited to the standard testing and rollout procedures already in place for kernel updates. No additional configuration changes are required beyond ensuring the system boots the newly installed kernel image.

The fix is scoped to the five listed kernel series; any kernel outside these versions, including custom or older long-term support releases, will not receive this correction automatically. Organizations that cannot upgrade these specific series will continue to run kernels with the regression and remain exposed to the underlying speculative-execution issue. Therefore, the benefit of the update is confined to systems that can adopt one of the provided stable releases.

From an operational standpoint, teams should verify compatibility of the new kernels with their hardware drivers and critical workloads before scheduling the reboot. Because the change is limited to a single bug fix, the risk of side effects is low, but regression testing remains prudent. Once validated, the upgrade restores the intended security posture and eliminates the instability introduced by the prior patch.