Good thing nobody is silly enough to let fully autonomous AI agents run as regular users on these affected operating systems. That could be disastrous given a zero day prompt injection technique.
[dead]
Copy Fail
221–230 of 545 posts
Re: Copy Fail
#222Earlier quoted context omitted.
Good writing for a broad audience requires it. Unfortunately the LLMs don't tend to adopt this guideline.
it’s a CVE write up; the audience for these knows what an LPE is.
That’s very optimistic. I’d bet there are an order of magnitude more people wondering how exposed they are than security researchers reading this.
Re: Copy Fail
#223I couldn't get the POC to work with my version of Python so I had ChatGPT convert it to C [0] and was able to verify my Slackware system does not appear to be affected, but my NixOS system would be if I had any world-readable suid binaries (which I had to make one to test it). [0] https://rkeene.org/viewer/tmp/copy_fail_exp.c.htm
Don't you have like, a sudo in /run/wrappers/bin?
EDIT: Sorry, I failed at reading your message. Never mind.
Re: Copy Fail
#224The page itself seems vibecoded and a bit of an advertisement, but it does look like the vulnerability is real and high risk. It does explain the big security update I just got, guess I'll prioritize updating today.
These guys don't need to advertise, they are already 100% busy with work. But who wastes their time manually creating web pages? Especially kernel devs.
Side comment: I have recently used Claude Code to make a few sites for testing purposes. In the prompt I added "don't make it look vibe coded," and it worked pretty well: No purple gradients, bento box layouts, etc. Nothing spectacularly original, either, but probably enough to avoid accusations of vibe coding.
Re: Copy Fail
#225I love how it says
"Standalone PoC. Python 3.10+ stdlib only (os, socket, zlib).
Targets /usr/bin/su by default; pass another setuid binary as argv[1]."
Except you can't pass another setuid binary as argv[1] because the AI writing this slop never added that feature to this python script.
I can't get it to work on any distro i've tried.
Re: Copy Fail
#226Earlier quoted context omitted.
Good writing for a broad audience requires it. Unfortunately the LLMs don't tend to adopt this guideline.
it’s a CVE write up; the audience for these knows what an LPE is.
I've read many CVEs (somehow that acronym is ok... heh) but have never seen LPE despite being familiar with the concept.
Re: Copy Fail
#227Earlier quoted context omitted.
> Disagree because to run the PoC you really ought to understand what it’s doing. that is contained in the report, which will look similar to the blog. the maintainers will have an open line of contact with the reporters as well. the poc is a small part of the entire report. its not like the linux maintainers only received this poc and have to work out the vulnerability from it alone. > It is failing at letting peopl…
what the blog says and what the code does are two different things. For all I know the blog itself is a honey pot. I need to know what the code does before I run it.
While your at it you can enter your credit card details to see if they've been leaked.
Re: Copy Fail
#228Earlier quoted context omitted.
Again, I think the point is that compressed size is a reasonable measure of the inherent complexity of a program. I'm a crap mathematician, but I believe that is a fundamental concept in information theory.
But it isn’t compressed size, the compressed part is only 180 bytes of the 732.
Ah, got it. Thank you.
Re: Copy Fail
#229Does anyone have a workaround for it? Edit: I don't understand why the comment would be downvoted.
I used, for debian based systems:
printf "# CVE-2026-31431\nblacklist algif_aead\ninstall algif_aead /bin/false\n" | sudo tee /etc/modprobe.d/blacklist-algif_aead.conf >/dev/null && sudo update-initramfs -uRe: Copy Fail
#230Good thing nobody is silly enough to let fully autonomous AI agents run as regular users on these affected operating systems. That could be disastrous given a zero day prompt injection technique.
I don't see what the issue is, my agent is already running as root.