new Linux LPE, this time using io_uring. I think it's good to point out this Google security blog from 2023. Sending all kernel commits into an LLM might be somewhat new, the mitigation measures are already old.

also I think io_uring is a very cool technology, it just has it's tradeoffs like everything. That's all :)

the LPE in case: https://github.com/v12-security/pocs/tree/main/pintheft

@eloy Another one? Again?

Can we just, y'know, have a break?

(I mean, I'm just going to ignore this for my personal stuff and just, well, see whatever happens or not. But I very much do not wish to be professional sysadmin right now, or possibly ever again)

also funny to realize that the main engineer behind io_uring is Jens Axboe, a software engineer employed at Meta. I wonder how intensely they use it in production there

@eloy I love io-uring, stop breaking io-uring

@eloy they forgot the -o in the first gcc invocation in the README (cd pintheft && gcc exp poc.c && ./exp)

@eloy for statistics on the distribution of areas where bugs are found, it does not really differ who (humans, LLMs or other tooling) finds it, right?

https://en.wikipedia.org/wiki/Io_uring#Security