This is almost 2 years old. FTA “The flaw impacts many major Linux distributions, including but not limited to Debian, Ubuntu, Fedora, and Red Hat, which use kernel versions from 3.15 to 6.8-rc1”
I ran hostnamectl on my current machine and got this:
Kernel: Linux 6.16.3-76061603-generic
Hopefully the other linux user chimes in here soon.
Debian Trixie is on 6.12. I would expect many Debian users to still be on Bookworm though, which is reported as “6.1 series”. Not sure if those would be affected. Most other distros will be on newer kernels than Debian.
Whichever kernel debian bookworm has, the patch for this has most likely been applied to it. The larger risk is to organizations running ancient versions of RHEL or something that never get updated, e.g. because some hardware they need uses a shitty proprietary driver that supports only very specific kernel versions.
Edit: You can confirm that it’s been fixed in Debian here. Looks like it was patched for bullseye systems still running kernel 5.10 in June 2024.
This is almost 2 years old. FTA “The flaw impacts many major Linux distributions, including but not limited to Debian, Ubuntu, Fedora, and Red Hat, which use kernel versions from 3.15 to 6.8-rc1”
I ran hostnamectl on my current machine and got this:
Kernel: Linux 6.16.3-76061603-generic
Hopefully the other linux user chimes in here soon.
Debian Trixie is on 6.12. I would expect many Debian users to still be on Bookworm though, which is reported as “6.1 series”. Not sure if those would be affected. Most other distros will be on newer kernels than Debian.
https://www.debian.org/releases/trixie/release-notes/whats-new.en.html
I don’t have any machines still running Bookworm so I can’t check for myself.
Whichever kernel debian bookworm has, the patch for this has most likely been applied to it. The larger risk is to organizations running ancient versions of RHEL or something that never get updated, e.g. because some hardware they need uses a shitty proprietary driver that supports only very specific kernel versions.
Edit: You can confirm that it’s been fixed in Debian here. Looks like it was patched for bullseye systems still running kernel 5.10 in June 2024.