- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
You must log in or register to comment.
Scarry! Uoi guys on windows better stay away…ohhh privilege!
what’s a scenario where you could suffer from this vulnerability?
Same workaround works here as with dirty frag. Just disable those kernel modules.
Maybe the solution is to just, delete a bunch of kernel modules.
How many of them are actually important anyway?
Good news. One fewer zero-day.
there is more where that came from https://xcancel.com/IntCyberDigest/status/2053802477019906058
It’s frustrating that there isn’t much of an effort to turn Linux into more of a microkernel. Instead the kernel just keeps getting bigger with even more subsystems and modules that can be exploited.
Systems built on microkernels exist, you know. See Redox.
https://redox-os.org/
Fuck it, taking my home server offline for a while.
Mainly because of the nginx RCE
At this point we might as well just run everything as root anyway
Leave ssh root access open with no password. Attackers will try to escalate privileges as their default strategy, when that fails they’ll add your IP to their unhackable blacklist.
😂😂😂
apparmor ftw
If this is quickly solved, there is nothing to worry about
Sorry if my english is bad
It is already solved. The dirtyfrag patch fixes it already.
Only think you forgot was punctuation marks at the ends of your sentences.
This simply means the person isn’t finished talking.
I think you might be able to deactivate this one by turning off XFRM support in a custom-configured kernel, at the cost of losing some types of tunneling. Not going to actually test that, though.
