How Debian Chooses Its Linux LTS Kernel Versions

This article examines how the Debian Kernel Team selects upstream Long Term Support (LTS) Linux kernels for inclusion in stable Debian releases. It details the alignment between Debian’s multi-year release schedules and upstream kernel releases, the technical criteria regarding hardware enablement and architecture support, and how maintainability drives the team's final decision.

Alignment with Upstream LTS Schedules

The primary factor in selecting a kernel version is the upstream Linux kernel release cycle, overseen by kernel maintainers like Greg Kroah-Hartman. Upstream designates typically one kernel per calendar year as an LTS release, usually the final release of that year.

Because Debian provides security support for a stable release for approximately three years—extended to five years with the Debian LTS project—the Debian Kernel Team strongly favors an upstream LTS release. Relying on an upstream LTS branch allows Debian to inherit critical bug fixes, driver improvements, and security patches without having to independently backport every fix from mainline development.

The Debian Freeze Window

Debian releases follow a strict milestone-driven freeze process: Transition Freeze, Soft Freeze, Hard Freeze, and Full Freeze. The kernel selection must fit within this window:

  1. Testing in Unstable: The kernel team introduces prospective kernel versions into Debian unstable (Sid) to discover regressions and packaging issues.
  2. Transition to Testing: The selected kernel must migrate into Debian testing before the Hard Freeze takes effect.
  3. Timing Compatibility: If an upstream LTS kernel is released shortly before the freeze begins (typically late winter or early spring of a release year), the team evaluates whether there is enough time to package, test, and stabilize it before the final release. If an upstream LTS is released too late in the freeze cycle, the team defaults to the preceding upstream LTS release.

Architecture and Hardware Compatibility

Debian is committed to supporting a wide range of hardware architectures, including amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, and s390x.

Before locking in an LTS candidate, the Debian Kernel Team ensures the version compiles and functions reliably across all official release architectures. Furthermore, the chosen kernel must provide sufficient hardware enablement for newer consumer and enterprise platforms while avoiding regressions on older, legacy systems supported by the distribution.

Upstream Coordination and Backporting Feasibility

The Debian Kernel Team maintains direct communication with upstream kernel developers. If a Debian release schedule falls between potential upstream LTS designations, the team assesses:

  • Official Upstream Commitment: Confirmation that upstream will maintain the branch for at least two to three years.
  • Maintenance Overhead: The workload required to maintain the kernel once upstream LTS maintenance ends, particularly when handing the release over to the Debian LTS team.
  • Backporting Security Fixes: The ease of applying stable tree patches and Common Vulnerabilities and Exposures (CVE) remedies over the Debian release lifecycle.

By synchronizing Debian's freeze schedule with the upstream Linux LTS calendar, the Debian Kernel Team ensures that each Debian stable release ships with a thoroughly tested, widely supported kernel that can be reliably maintained for years.