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.
I read: Microsoft started to feel threatened and paid black hats to exploit vulnerabilities in wares that people have recently learned are far superior to their goddamned surveillance garbage.
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
Yes, but still a privilege elevation bug is still less risky than a remote execution one.
They're replying to the victim blaming mentality of "if you let them then you have bigger problems" in your comment. Not your point about it being less dangerous than remote execution.
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.
RHEL is on 5.15 in spirit only. They backport tons of patches to the point that 5.15 modules don't build against it
I think RHEL9 uses 5.14 as base
You’re right, it’s 5.14 not 5.15 like I thought. I’m spending most of my time im Debian these days though, so I’m glad I wasn’t too far off.
They will probably have a version newer than 5.15.149.
AliasAKA is correct, it’s actually 5.14, not 5.15 like I thought.
fuck my phone running android is vulnerable
Feeling pret-ty smug about my Windows 10 machine rn ngl
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.
And that kids, is why we are pushing for Rust in the Kernel
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 😭😭😭
But then the kernel wouldn't be free! Free as in 'use-after-free'!
(/s in case it wasn't obvious)