If you don't have the algo_aead kernel module enabled, are you still vulnerable to this? Any systems don't show it in lsmod whenever I've tried, does that mean most computers are OK?
Though this is a severe exploit, note that you need already user access to the machine to use it.
Dor like ... Everyone here who learns from it cis this need it's likely a non issue. Still good practice to fix but if you didn't share your user space this will not be the attack vector you will fall victim to - most likely.
Any one of the programs or docker containers you run has user access. Now any of them could have root access unchecked. You can't know you haven't installed an update with malicious code to any one of the hundreds of packages a desktop install has.
If I understand correctly, this could be exploited to escape linux namespaces, which which are the foundation of containers like Flatpak and Docker. Those were never very good security boundaries, but running untrusted code in them is now especially dangerous, until your kernel is patched.
I suppose this is why my computer updated when I booted it up yesterday. And then I had to update and reboot. Then after I rebooted I had to logout to install extension updates. Then I I had more updates that required another reboot!
Big thanks to all the people that patched this so quickly, what a huge batch of updates!
...I am not complaining, I think it's pretty cool and a bit funny.
Just to note, if you are on an LTS version (which many people running servers will be), it's likely an upgrade will not solve this. In which case you should check your installed version and if not yet corrected, disable that module. For most people it is not used anyway.
According to comments on Lobsters, the distros weren't notified prior to publication, so any backports took longer than usual.
According to Greg K-H, nobody typically gets notified by the Linux kernel team about anything, so this is not abnormal: https://www.openwall.com/lists/oss-security/2026/05/01/3
Distro maintainers should be monitoring the lists and feeds and making decisions themselves, not expecting spoon-feeding from the kernel team.
Yes, but the researchers should have notified the linux-distros mailing list as well per the published policy. See https://docs.kernel.org/process/security-bugs.html#coordination-with-other-groups
It's unfortunate, but understandable why this didn't happen. Still, the researchers claimed in their blog post that fixes were shipping, apparently without actually checking.
I dont get it, doesn't responsible disclosure mean the distros get the packages out first?
Nothing about this disclosure was responsible.
https://xint.io/blog/copy-fail-linux-distributions#coordinated-disclosure-timeline-8
It was patched a month ago.
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.
Thanks, done.
uname -rmv
6.12.85+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.85-1 (2026-04-30) x86_64
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.