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
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
fuck my phone running android is vulnerable
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.
AliasAKA is correct, it’s actually 5.14, not 5.15 like I thought.
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.
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.?
How would I know what kernal I have?
With the uname -a command
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 😭😭😭
Rust would not of fixed this
Rust isn't magical
Explain how a use after free could occur in safe rust, because to my knowledge, that is exactly the kind of thing rust does protect against.
Duh, by wrapping it in an unsafe block.
Boom.
You never say "would not of". It's "would not have".
Rust would have prevented this, because the borrow checker prevents use-after-free vulnerabilites.
Do you know what a use-after-free bug is? Rust was literally designed to make this type of memory bug impossible.
But then the kernel wouldn't be free! Free as in 'use-after-free'!
(/s in case it wasn't obvious)
Magical pills do not exist. Better start pushing old fuckers incapable of learning out of the project (yeah, I don't like this kind of treatment of Rust just because it is not C either)
Old fuckers exist to protect young fuckers from throwing out the baby with the bath water.
I'm referring to the ageism implied in the statement, I don't care about C vs Rust any more than I care about vi vs emacs or KDE vs Gnome.
Old fuckers have experience, they have seen many next big things come and go, that's why they seem slow to adopt new stuff. Of course this annoys new fuckers a lot, as they want to play with their new shiny toys now.
Patience is a virtue, young grasshopper.
Ooh, so "get out with this Rust, I ain't gonna think about when writing my code" is protecting a baby now?
Okay, then why we need to use a language that has more in common with OCaml? What about using a better C instead?
Such as?
This language was there for a lot longer than Rust, and is not "OCaml, but with curly braces for scopes".
no one uses d
It's never too late to start!
let me clarify: no employer uses d. I use d. I am a nobody
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.
Feeling pret-ty smug about my Windows 10 machine rn ngl
Your Windows 10 machine? Microsoft disagree.
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.
That one time that Clippy started peeling off it's flesh whilst chanting in reversed Latin and also wasn't in the computer anymore.
(This was after I let it play that Flash with the Badger song for two weeks so I kinda understand what happened.)
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.
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.