view the rest of the comments
Linux
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.
Though this is a severe exploit, note that you need already user access to the machine to use it.
Dor like ... Everyone here who learns from it cis this need it's likely a non issue. Still good practice to fix but if you didn't share your user space this will not be the attack vector you will fall victim to - most likely.
Any one of the programs or docker containers you run has user access. Now any of them could have root access unchecked. You can't know you haven't installed an update with malicious code to any one of the hundreds of packages a desktop install has.
If I understand correctly, this could be exploited to escape linux namespaces, which which are the foundation of containers like Flatpak and Docker. Those were never very good security boundaries, but running untrusted code in them is now especially dangerous, until your kernel is patched.