Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.
For exploiting a privilege escalation the attacker must be able to run their own code on your machine. If you let them do such things, you already have more than enough security problems in the first place.
Except for supply chain attacks. You get a foot in the door, and open the rest with impunity
Feeling pret-ty smug about my Windows 10 machine rn ngl
Lol because Windows has never been exploited
Name literally one time!?
This is a joke right
I hacked it. The screen said “It is now safe to turn off your computer.” but I left it on instead.
This only affects positively ancient kernels:
From (including) 3.15 Up to (excluding) 5.15.149 From (including) 6.1 Up to (excluding) 6.1.76 From (including) 6.2 Up to (excluding) 6.6.15 From (including) 6.7 Up to (excluding) 6.7.3
If I’m not mistaken, RHEL9 and equivalents are on 5.15. That’s a pretty big blast radius.
They will probably have a version newer than 5.15.149.
fuck my phone running android is vulnerable
Debian Bookworm (Debian 12/oldstable) would be affected then, I think?
It looks to be on 6.1.153 currently which is much newer than 6.1.76.
Sweet, cheers for checking - I just remembered it being on 6.1.?
Local attacker? So on your LAN
You need to be able to run code on the system that has the bug. The bug is in the netfilter component, in how it's managed on that system, not in the actual traffic flows.
So a non issue unless somebody has physical access to the machine?
Unfortunately, it's not that simple, because attacks often involve "exploit chains". In this case, an attacker would use a different vulnerability to gain code execution capability, and then use that capability to exploit this vulnerability.
Update your systems, folks.
Understood
And that kids, is why we are pushing for Rust in the Kernel
But then the kernel wouldn't be free! Free as in 'use-after-free'!
(/s in case it wasn't obvious)
But... You dont understand, Rust is the devil! If Rust were made the kernel's main language it would terrible because that would mean change 😭😭😭