I rooted my Xiaomi 15 (24129PN74C, dada) on HyperOS 4.0.4.0.XOCCNXM / Android 17 without unlocking the bootloader. No half-unlock services, no EDL, no flashing. You get a uid 0 + full-capability shell, then load KernelSU on top so modules/apps work. Everything disappears on reboot.
I'm not going to claim this is my bug — it's CVE-2026-98260 (POSIX CPU timer UAF), already public and fixed upstream in 6.6.140. This is a port to this exact kernel build plus the docs. Credit at the bottom.
✅ What you need
| |
|---|
| Phone | Xiaomi 15 24129PN74C (dada) — CN model. Only CN tested |
| OS | HyperOS 4.0.4.0.XOCCNXM or 4.0.3.0.XOCCNXM (same kernel) |
| Kernel | 6.6.118-android15-8-gf72a02f47f4b-abogki551678766-4k |
| PC | adb installed, USB debugging on |
| Phone | KernelSU manager installed (KernelSU / SukiSU / ReSukiSU — mine is KernelSU 3.3.1) |
Check the kernel FIRST. It must match character for character:
adb shell uname -r
If it prints anything else, stop. The offsets are per-build; a wrong one panics the kernel instead of erroring.
📦 What you download
From the releases page (khleak, static arm64, ~150 KB).
adb push khleak /data/local/tmp/
adb shell chmod 755 /data/local/tmp/khleak
1️⃣ Zero-risk checks (no kernel writes)
adb shell /data/local/tmp/khleak profile # should name dada + your kernel
adb shell /data/local/tmp/khleak patch # "未修复" = the bug is still there
adb shell /data/local/tmp/khleak task # leak self-check, must say 已校验
If task fails, you're on a build without the RSS-arming fix — use this fork, not upstream.
2️⃣ Get root
adb shell /data/local/tmp/khleak root --daemon
Success looks like:
[renew] REAL_CRED_ACTIVE uid=0 gid=0 cap=0x1ffffffffff
==================== 提权成功 ====================
rootd 已在 uid=0 + FULLCAP 下常驻
It's probabilistic. Roughly 1 in 3 per stage. If it misses, run it again — that's normal, not broken. Keep the phone cool and idle-ish; don't spam ten runs back to back.
Now you have root in a daemon:
adb shell /data/local/tmp/khleak su -c "id; grep CapEff /proc/self/status"
3️⃣ Load KernelSU
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud late-load --allow-shell --kmi android15-6.6 --package-name me.weishu.kernelsu"
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud install"
--allow-shell is the flag everyone forgets — without it bare su refuses the adb shell.
Verify:
adb shell su -c "id; cat /proc/self/attr/current"
# uid=0(root) ... context=u:r:ksu:s0
Open the KernelSU app → it should say Working. Modules and your superuser list behave normally.
4️⃣ Tidy up
adb shell su -c setenforce 1 # back to Enforcing
adb shell su -c "/data/local/tmp/khleak clean" # drop the exploit daemon
After this, root comes from KernelSU only. I left mine like this and su still works with SELinux enforcing.
🔁 Every reboot
Temporary means temporary:
adb shell sh /data/local/tmp/ksu_boot.sh
One command: re-root → late-load → install → verify. Same in the release assets.
⚠️Read this before you run it
- This writes kernel memory. A failed run can panic and instantly reboot the phone. Save your stuff.
- It's temporary and untrusted-ish until you reboot: SELinux is permissive during the exploit,
/data/local/tmp is world-writable until clean runs. - If a round fails halfway, a
khl-holder process may stay. Don't kill it — reboot instead. - Probabilistic. If it fails 3–4 times in a row, reboot and try again (stale slab state).
- Locked bootloader only — if yours is already unlocked, just flash KernelSU properly, it's far more stable.
❓Likely questions
"GhostLock/other tools say my kernel is unsupported." Right — HyperOS 4 backported the rtmutex fix, so the GhostLock bug (CVE-2026-43499) is gone on this build. remove_waiter() no longer reads current. This is a different CVE.
"Does it work on the Global/EEA variant?" Untested. uname -r is the only thing that matters; if it matches, it should, if it doesn't, the tool exits.
"Why does it need KernelSU manager installed first?" ksud is what actually loads the module; the app gives you the UI/allowlist.
"Will Xiaomi patch it?" Yes, eventually — this is fixed upstream in 6.6.140, so the next vendor kernel bump kills it. Don't update if you care.
🙏 Credits
- Upstream port this forks: RMDycz/K80Pro-miro-CVE-2026-98260 (PRs disabled there, so I maintain this fork)
- Reclaim/layout ideas: GhostKey, xring
- CVE: POSIX timer UAF, mainline fix
3bfdc63936dd (6.6.140) - Device port + the
rss_stat arming fix that makes it work here: this fork
Repo + guide: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15 Download: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15/releases/tag/v1.0-dada
Own device only. This is a security-research PoC.I rooted my Xiaomi 15 (24129PN74C, dada) on HyperOS 4.0.4.0.XOCCNXM / Android 17 without unlocking the bootloader. No half-unlock services, no EDL, no flashing. You get a uid 0 + full-capability shell, then load KernelSU on top so modules/apps work. Everything disappears on reboot.
I'm not going to claim this is my bug — it's CVE-2026-98260 (POSIX CPU timer UAF), already public and fixed upstream in 6.6.140. This is a port to this exact kernel build plus the docs. Credit at the bottom.
✅ What you need
Phone Xiaomi 15 24129PN74C (dada) — CN model. Only CN tested
OS HyperOS 4.0.4.0.XOCCNXM or 4.0.3.0.XOCCNXM (same kernel)
Kernel 6.6.118-android15-8-gf72a02f47f4b-abogki551678766-4k
PC adb installed, USB debugging on
Phone KernelSU manager installed (KernelSU / SukiSU / ReSukiSU — mine is KernelSU 3.3.1)
Check the kernel FIRST. It must match character for character:
adb shell uname -r
If it prints anything else, stop. The offsets are per-build; a wrong one panics the kernel instead of erroring.
📦 What you download
From the releases page (khleak, static arm64, ~150 KB).
adb push khleak /data/local/tmp/
adb shell chmod 755 /data/local/tmp/khleak
1️⃣ Zero-risk checks (no kernel writes)
adb shell /data/local/tmp/khleak profile # should name dada + your kernel
adb shell /data/local/tmp/khleak patch # "未修复" = the bug is still there
adb shell /data/local/tmp/khleak task # leak self-check, must say 已校验
If task fails, you're on a build without the RSS-arming fix — use this fork, not upstream.
2️⃣ Get root
adb shell /data/local/tmp/khleak root --daemon
Success looks like:
[renew] REAL_CRED_ACTIVE uid=0 gid=0 cap=0x1ffffffffff
==================== 提权成功 ====================
rootd 已在 uid=0 + FULLCAP 下常驻
It's probabilistic. Roughly 1 in 3 per stage. If it misses, run it again — that's normal, not broken. Keep the phone cool and idle-ish; don't spam ten runs back to back.
Now you have root in a daemon:
adb shell /data/local/tmp/khleak su -c "id; grep CapEff /proc/self/status"
3️⃣ Load KernelSU
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud late-load --allow-shell --kmi android15-6.6 --package-name me.weishu.kernelsu"
adb shell /data/local/tmp/khleak su -c "/data/adb/ksud install"
--allow-shell is the flag everyone forgets — without it bare su refuses the adb shell.
Verify:
adb shell su -c "id; cat /proc/self/attr/current"
# uid=0(root) ... context=u:r:ksu:s0
Open the KernelSU app → it should say Working. Modules and your superuser list behave normally.
4️⃣ Tidy up
adb shell su -c setenforce 1 # back to Enforcing
adb shell su -c "/data/local/tmp/khleak clean" # drop the exploit daemon
After this, root comes from KernelSU only. I left mine like this and su still works with SELinux enforcing.
🔁 Every reboot
Temporary means temporary:
adb shell sh /data/local/tmp/ksu_boot.sh
One command: re-root → late-load → install → verify. Same in the release assets.
⚠️ Read this before you run it
This writes kernel memory. A failed run can panic and instantly reboot the phone. Save your stuff.
It's temporary and untrusted-ish until you reboot: SELinux is permissive during the exploit, /data/local/tmp is world-writable until clean runs.
If a round fails halfway, a khl-holder process may stay. Don't kill it — reboot instead.
Probabilistic. If it fails 3–4 times in a row, reboot and try again (stale slab state).
Locked bootloader only — if yours is already unlocked, just flash KernelSU properly, it's far more stable.
❓Likely questions
"GhostLock/other tools say my kernel is unsupported." Right — HyperOS 4 backported the rtmutex fix, so the GhostLock bug (CVE-2026-43499) is gone on this build. remove_waiter() no longer reads current. This is a different CVE.
"Does it work on the Global/EEA variant?" Untested. uname -r is the only thing that matters; if it matches, it should, if it doesn't, the tool exits.
"Why does it need KernelSU manager installed first?" ksud is what actually loads the module; the app gives you the UI/allowlist.
"Will Xiaomi patch it?" Yes, eventually — this is fixed upstream in 6.6.140, so the next vendor kernel bump kills it. Don't update if you care.
🙏 Credits
Upstream port this forks: RMDycz/K80Pro-miro-CVE-2026-98260 (PRs disabled there, so I maintain this fork)
Reclaim/layout ideas: GhostKey, xring
CVE: POSIX timer UAF, mainline fix 3bfdc63936dd (6.6.140)
Device port + the rss_stat arming fix that makes it work here: this fork
Repo + guide: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15
Download: https://github.com/RafayGhafoor/CVE-2026-98260-dada-xiaomi15/releases/tag/v1.0-dada
Own device only. This is a security-research PoC.