Ok this is the first time I try one of these exploits and it works on my system, I'm currently very spooked.
On the other hand, this may allow me to root my LG WebOS TV?
this post was submitted on 07 May 2026
182 points (97.4% liked)
Linux
65117 readers
873 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
Now that i Didn't consider
Nice, you could change the os
I tried on nixos and did not work, but maybe the paths needs adjustments
Can't wait for one that'll work on Android so I can maybe root some otherwise useless old phones
What would you use the old phones for out of curiosity?
I'm keen to put PostmarketOS on them all and build a Kubernetes cluster. Just don't ask me what I'm going to run on it!
Removing all the system-level bloat that makes them unpleasant to use, perhaps stripping one down to the level of a fancy MP3 player with its microSD slot. Also having "disposable" phones to play with various rooted tweaks. All of my easily-rootable phones are too valuable as daily drivers to experiment on, while all of the ones I don't care about also don't have rooting methods yet.
I've encountered a couple of people who use them as remote cameras to observe their 3D printers. That suggests a bunch of other possibilities for things you want to be able to watch or listen to without standing over them and without buying an extra webcam to cover what might be a temporary need.
A middle finger to those you're jailbreaking from.
They are less expensive.
EDIT:
Sorry, I misread the parent comment.
You would use them for literally anything you typically or potentially could use a phone for.
If you are not playing video games on your phone... there is basically no common reason to have a top spec brand new phone.
What do I want my phone to do?
Make calls, send messages, run a web browser, check emails, take a picture or video every once in a while, act as a notepad, check a weather forecast, have some map explorer, use some entirely 2D proprietary apps for things like... groceries or hailing a ride or checking my bank balance.
Pretty sure that right there is about 80% of people's phone use case.
You do not need top spec hardware to do any of that.
You have the gaming thing to do the gaming stuff.
I'm not the person you replied to, but I would love to have more ARM hardware for running tests on. A lot of what I write needs to be separately tested on each architecture.
Update: Kernel 7.0.5 just released
Fixes: cac2661c53f3 ("esp4: Avoid skb_cow_data whenever possible")
Fixes: 03e2a30f6a27 ("esp6: Avoid skb_cow_data whenever possible")
Fixes: 7da0dde68486 ("ip, udp: Support MSG_SPLICE_PAGES")
Fixes: 6d8192bd69bb ("ip6, udp6: Support MSG_SPLICE_PAGES")
In the 90s I compiled all my kernels at home from source with just the drivers I needed. Only installed the packages I needed. Only enabled the services I needed. The Unix way. When the kernel added modules I was still only compiling a subset and generally loading them manually.
Obviously that doesn't work for most users and distros sensibly started shipping with modules compiled for practically every need. Usually when I view distro security alerts they are for packages I don't install. But I have all these damn kernel modules just waiting to automatically load. I know I can blacklist them individually but I wonder if there is a way to profile the modules I use and use a deny all/whitelist approach instead?
modprobed-db can create a profile of the kernel modules that get loaded by your system over time. You can feed that directly into make localmodconfig to build a kernel that only includes those modules, or use the data to build a modprobe whitelist.
Hm? Somehow, lemmy.zip messed up the proxying, (clickable link)? Good thing you've pasted it plaintext.
Hahaha no I'm just an idiot and accidentally swapped the url and text, thanks for catching that - fixed now
load more comments
(1 replies)
load more comments
(2 replies)
It was patched in almalinux though, and it was how this exploit got exposed before disclosure.
At lest this is what I read
Good to see these exploits being found and worked on
This was leaked early. There is a mitigation (see link for confirmation):
sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"
load more comments
(1 replies)
may become useful if i forgot my password.
Or somebody else’s password
view more: next ›