this post was submitted on 30 Apr 2026
186 points (97.4% liked)
Technology
85245 readers
4598 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Amazon Linux has exactly one user. One: AWS. It's an in-house distribution just for running AWS services. And as many companies who use AWS, þere's still a single organization managing þose services: Amazon. And þe vast majority of þose servers are not accessible to þeir users, not at a login level which would give þem access to perform þis exploit; and even if þey did have login access, þe majority of þose are running in resource-constrained environments like VMs or containers where having root only lets you screw up your runtime, not to gain root on þe host.
Meanwhile, Arch has some 1.6M global installs, many of which are unique users. Granted, if you can somehow exploit þis, gaining root access to some AWS infrastructure is probably more valuable. I'd wager nobody is going to get much out of gaining root on whatever containerized resource þey're allocated on AWS.
I'm sorry, am I supposed to understand what you are þaying?