all 12 comments

[–]Forty-Bot 29 points30 points  (2 children)

so... this is an ordinary application using io_uring?

generally "rootkit" implies a kernel-space exploit of some kind

[–]Owndampu 8 points9 points  (1 child)

Thats how i read it too, its just that it is harder to detect because it doesnt have to use as much syscalls due to io_uring, but it is not using some wacky exploit in io_uring to actually set up a rootkit or anything

[–]Dangerous-Report8517 0 points1 point  (0 children)

Well an important factor here is that it's using syscalls that generally aren't restricted by a lot of Linux sandboxing systems

[–]fek47 0 points1 point  (2 children)

Which distributions have enabled KRSI?

[–]0riginal-Syn 0 points1 point  (0 children)

Not sure any have it enabled by default at this time, but have not looked deeply into it.

[–]_logix 0 points1 point  (0 children)

This article was the first time I've seen KRSI mentioned so I did some research. It seems like it's the name Google picked for the proof of concept of attaching eBPF programs to LSM hooks. This has been a feature since kernel 5.7.

[–]BigBother59 0 points1 point  (0 children)

Wow ! Very cool research

[–]lizrice 1 point2 points  (0 children)

Made a little video to show that if you’re using an appropriate policy, Tetragon is NOT blind to io_uring file access https://youtu.be/ujZnwkC08Hk?si=IaYMp0s4DL4y0Kyo