this post was submitted on 30 Apr 2026
159 points (99.4% liked)

Linux

13472 readers
457 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
159
The same 732-byte Python script roots every Linux distribution shipped since 2017 (copy.fail)
submitted 1 day ago* (last edited 1 day ago) by not_IO@lemmy.blahaj.zone to c/linux@programming.dev
28 comments fedilink hide all child comments
 

woaw

also a good blog post about it https://xint.io/blog/copy-fail-linux-distributions

you are viewing a single comment's thread
view the rest of the comments
[–] stuner@lemmy.world 9 points 1 day ago (2 children)

It seems that most LTS distros didn't get a heads up and there are no patches available. Uh oh.

[–] woelkchen@lemmy.world 2 points 11 hours ago (1 children)

Automated test suites became so good, many regular people can just use rolling release distros these days.

[–] stuner@lemmy.world 3 points 7 hours ago (1 children)

That may be true for personal computers, but the impact of this vulnerability is mainly on servers. And those typically run distros like Debian, Ubuntu, RHEL that didn't have a patch at that time.

[–] woelkchen@lemmy.world 3 points 6 hours ago

the impact of this vulnerability is mainly on servers

The impact is any Linux install without root access for its users.

[–] superglue@lemmy.dbzer0.com 2 points 20 hours ago (2 children)

What I read said the patch was merged into main on April 1st, so they should have.

[–] stuner@lemmy.world 3 points 7 hours ago (1 children)

It looks like the fixes were merged in 6.18, 6.19, and 7.0. But all older (but supported) LTS kernels didn't have the fix, like 6.12, which is used in Debian 13. And it also seems that Ubuntu, RHEL, and SUSE had not picked up the patches in their kernel versions.

[–] Successful_Try543@feddit.org 3 points 5 hours ago* (last edited 5 hours ago)

The kernel 6.12.73-1 used by Debian Trixie is still vulnerable. Applying security updates should update the kernel to 6.12.85-1 and fix the issue.

https://security-tracker.debian.org/tracker/CVE-2026-31431

[–] lengau@midwest.social 4 points 11 hours ago

This thread gives a good rundown of what happened: https://infosec.exchange/@wdormann/116489443704631952