view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Most LTS distros have security updates enabled ootb.
I mean I updated my servers and some of them on LTS releases that were not the very latest one were still vulnerable after a reboot. Hence I disabled the module on those servers. So it's worth checking your version definitely has a fix available.
Which?
~~It could be for example Debian 12 (Bookworm). While Debian 13 (Trixie) already got fixed, Bookworm is still vulnerable.~~
Edit: It just got fixed.
https://security-tracker.debian.org/tracker/CVE-2026-31431
Yeah one of them was Debian 12 for sure.