r/androidroot • u/thebesyplayerof • 6d ago
News / Method Found exploit that lets user gain root access temporarily.
The exploit is based on CVE-2026-98260. Working on kernel version 6.6.118. requires shizuku .
9
u/Icy_Till3223 5d ago
These people larp like they found a new LPE. You used a chain to execute an already existing (and patched) LPE on an older kernel. Say it right.
5
u/47th-Element 6d ago
The title is misleading, "found" implies you did the security research and discovered the vulnerability, which you didn't.
1
u/helloeverybodymynam 6d ago
DUDE! I have the exact same kernel version and I really need my temp root back, could you help me please?
1
1
1
u/Timely_Criticism4010 6d ago
Man 6.6 is kinda hard to get it but this looks fun tho
2
u/Amool_Doodh 5d ago
Lol.. my gt 7t runs on 6.6 upstream kernels and it's way easier.. 6.1 upstream kernels are the most unaffected by vulnerabilities
2
1
u/Timely_Criticism4010 5d ago
I mean till date 5.4 is the most stable. Since 6.1 has many instabilities and so is 6.6 due to similarities
1
1
u/Fire_in_Barf 5d ago edited 5d ago
Ahhh , good to see timer root getting traction. Used it on my device . Sad that the original timer root poc creator for android took it down or was taken down , and timer root has good success rate than ghostlock , this just requires a shell is the bad part
1
1
u/Original_Thing8770 Redmi note 8 pro, Infinity X; Pixel 9a, ghostlock root 5d ago
For those who are wondering it's called TimerRoot
1
1
u/ilovetopulsate 4d ago
I don't understand why you would just want a temporary root. Even kind of crazy. For what? What would you do with a temporary root?
1
u/VV_Syzta 3d ago
like chroot on termux,or droidspace for linux space to run pc stuff,or edit cpu clockspeed to be higher for phone cooling user, stuff like that,most people root for custom rom so it's understandable if they (maybe including you) dont care on this stuff
1
u/Impossible-Ad-8162 2d ago
None of the things you pointed out should be done using temp root, I have been developing roms, kernels and stuff for my device for years and one thing I would hate it to modify my system without knowing if that change is gonna boot next time or not.
Imaging accidentally removing only one thermal file because you wanted more perf, now you have a device which is permanently bricked until you get edl flashed [which btw might or might not be rejected by the official service center]
My words might not sound dangerous but believe me these things in a hand of normal people is dangerous as hell.
1
u/VV_Syzta 2d ago
then it would be used error if something wrong rather than temp root fault ,everything required user to know what they are doing
if the system modified would be problem on reboot, then just fix it back before boot,the whole point of temp root is that you cant permanent root,so if you expected it to be as convenient as permanent root then it missing the entire point of temp root
also thing like chroot didnt edit anyfile,what do you mean "none of the things you pointed out should be done using temp root"
1
u/Impossible-Ad-8162 2d ago
Nobody is blaming the exploit. Even I have helped users use it in my community with an explicit warn of how it works but the truth is something like this in the hands of a clueless person is dangerous as simple as that. If we start saying everything is userfault and do not weight the pros and cons of it then by that logic we should openup everything for everyone.
1
u/VV_Syzta 2d ago
everything user did wrong is indeed user error?this term was always there in tech vocabulary...
its the pro and cons itself that user have to know,yes we do weight,user has to,so they would know what cons is,if user didnt know about the cons,then mess up,thats user fault for not research it enough to know the cons of them
so if clueless person did something wrong without enough research,it is indeed their fault,you understand me correctly,the only exception is when they already did research but mess up due to something new, but that would apply to everything,temp root or not
1
u/Impossible-Ad-8162 2d ago
Agreed on this point, I am just stating the fact that many things exist that can be put off as user errors but as a dev it's my part to avoid putting it in those hands. If they get it even then that's their headache.
1
u/VV_Syzta 2d ago
it's my part to avoid putting it in those hands
nothing wrong trying to warn some cons,its just that your statement on your first reply here:
none of the things you pointed out should be done using temp root
which mislead into thinking that it is temp root fault,even tho we both agree that if something goes wrong it usually user fault
if your statement become like "you should be careful using temp root,its good if you know what you doing,but dont assume any permanent root thing work on temp root" i would be more appreciate
1
u/Impossible-Ad-8162 2d ago
Yeah, was just communication gap π€£π€£. Anyways finally we both can understand each other. Maybe my words were more generalized due to the fact that I though of it as a person who has to distribute it and you thought it as someone who has to use it.
1
u/Joudheyo 48m ago
The same happened to me once (the EDL one) and I could restore it using SamFW tool on Windows
1
2
u/ts_acc_doesnt_exist 6d ago
Permissive SELinuxπππ
1
u/thebesyplayerof 6d ago
π
1
u/Fire_in_Barf 5d ago edited 5d ago
Why keeping selinux permissive ? I too use this exploit but i am able to change it to enforcing without any issue,Β



8
u/Itz_Raj69_ 6d ago
Woah new temproot vuln?! this is fire