lol, lmao?? this AI generated website makes me wanna headbutt a wall but the CVE seems real(?), update your kernels folks
the part that really grinds my gears is why is the poc written in the most disgusting possible python syntax?? are we optimising for size here?
@cas the CVE is real - you can just run the PoC as proof of that much
are we optimising for size here?
apparently yes, expressly so - they seem very proud of the whole "732 Bytes to Root" thing
@cas it may be a way to avoid giving away other hints of how this issue was introduced or otherwise to avoid giving people ideas about other places to look in the kernel for latent vulnerabilities
@hipsterelectron it's not obfuscated, seems like they actually did optimise for size which is completely insane to me
@cas @hipsterelectron should've first published the exploit on npm as a module -> shorter code, just include module -> profit
@hipsterelectron @cas they're pretty forthcoming in the full writeup (https://xint.io/blog/copy-fail-linux-distributions) with a section on how this happened (i.e. across several independently sane patches) and how they found it:
Taeyang Lee's earlier kernelCTF work had mapped out the
AF_ALGattack surface. He realized thatAF_ALG+splicecreates a path where unprivileged userspace can feed page cache pages directly into the crypto subsystem and suspected that scatterlist page provenance may be an underexplored source of vulnerabilities.[AI tool sales pitch]
splice is a cursed syscall in general IMO, this is not the first (https://dirtypipe.cm4all.com) and probably won't be the last time something Gets It Wrong
@cxberger @hipsterelectron yeah i just zone out immediately when the "this was written by AI" detector goes off in my brain and then close the tab...
@cas they are clout chasing so much that they need to claim "exploit in X bytes" and all the other crap. no idea why it matters that you don't need to recompile for different kernel versions and similar things