The most recent Linux kernel releases are: 7.1, 7.0, 6.19, 6.18, …:<p>* <a href="https://en.wikipedia.org/wiki/Linux_kernel_version_history" rel="nofollow">https://en.wikipedia.org/wiki/Linux_kernel_version_history</a><p>7.0 is already present in <i>forky</i> (current <i>testing</i>), and available as a backport for <i>trixie</i> (current <i>stable</i>):<p>* <a href="https://packages.debian.org/search?keywords=linux-image-amd64" rel="nofollow">https://packages.debian.org/search?keywords=linux-image-amd6...</a><p>* <a href="https://packages.debian.org/trixie-backports/linux-image-amd64" rel="nofollow">https://packages.debian.org/trixie-backports/linux-image-amd...</a><p>The default kernel for <i>trixie/stable</i> is 6.12, initially released in November 2024, and officially supported upstream until December 2028.
It’s fairly easy to build your own kernel packages from vanilla sources in Debian. I’m running the latest 7.0.x within a few hours of its release. The build takes about 30-45 minutes depending on how much time I spend on skimming the ChangeLog. YMMV.
Wouldn't Forky/14 have this or newer when it releases next year? Debian moves slow - deliberately so, if you want fast use Arch or Fedora - but it does move.
Not a serious question but I'll give a serious answer anyway.<p>The last time I worried over which kernel was used in Debian Stable was... never. If I want a more recent kernel I run Debian unstable (Sid) which currently is at 7.0.12 (the current 'stable' kernel where 7.1 is 'mainline') but on my servers Stable (currently 'Trixie') does just fine with its 6.17.3 kernel. Debian 'Forky' will be released somewhere in 2027 with either a 7.0.x or 7.1.x kernel depending on how things go. The current kernel used in 'testing' (which will become 'stable' on the next release) is 7.0.10.
People don't usually understand that apt allows you to configure multiple sources across versions simultaneously, so you can e.g. run stable, but also selectively install from backports or unstable.<p>To do so, add the sources for trixie-backports and unstable, and add the following configuration (e.g. /etc/apt/preferences.d/trixie-sid-pin) so that the system knows which sources your prefer:<p><pre><code> # Default to trixie
Package: *
Pin: release n=trixie
Pin-Priority: 990
# Very low priority for sid
Package: *
Pin: release n=unstable
Pin-Priority: 100
# Give backports medium priority
Package: *
Pin: release n=trixie-backports
Pin-Priority: 500
</code></pre>
Now the system can access the latest kernel from unstable (and backports), while keeping everything else on stable:<p><pre><code> # apt policy linux-image-amd64
linux-image-amd64:
Installed: 7.0.12-1
Candidate: 7.0.12-2
Version table:
7.0.12-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
*** 7.0.12-1 100
100 /var/lib/dpkg/status
7.0.10-1~bpo13+1 500
500 http://deb.debian.org/debian trixie-backports/main amd64 Packages
6.12.90-2 500
500 http://security.debian.org/debian-security trixie-security/main amd64 Packages
6.12.86-1 990
990 http://deb.debian.org/debian trixie/main amd64 Packages
</code></pre>
I believe the kernel in backports gets updated only after it is live in unstable for at least a week, which lately still feels like forever.