Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
ksu-root — 在 REDMI K90 Max(代号 prague / OS4.0.0.14)上,从手机端一键开一个临时 root。利用 CVE-2026-64560(posix-cpu-timers UAF)加载 KernelSU LKM,重启即失效。不需要电脑、不刷机、不解锁 Bootloader。 | Kitploit
Tools/GitHubGitHub/wanwuzhishi/ksu-root
Android SecurityPrivilege EscalationPersistence MechanismsExploitationMobile App PentestingPost-ExploitationMobile SecurityPayload DevelopmentBinary Exploitation
GitHubwanwuzhishi/ksu-root

ksu-root

51211 days agoNot yet reviewed
Share

在 REDMI K90 Max(代号 prague / OS4.0.0.14)上,从手机端一键开一个临时 root。利用 CVE-2026-64560(posix-cpu-timers UAF)加载 KernelSU LKM,重启即失效。不需要电脑、不刷机、不解锁 Bootloader。

View Repository

KSU Root

On the Redmi K90 Max (codename prague, OS4.0.0.14 / OS4.0.5.0), open a temporary root with one tap from the phone. No computer, no flashing, no Bootloader unlocking required. It expires on reboot.

Download: Latest APK · Current version v1.1.0

Project introduction: KSU Root: Giving the Redmi K90 Max a temporary root that disappears on reboot — the author's blog, which walks through everything below; it's best to read this first before diving into the details.

Main interface Risk confirmation Run log About About - Credits


What this is

It packages the computer + adb privilege-escalation workflow from prague-CVE-2026-64560-OS4.0 into an Android App:

What you originally had to do on a computerNow just one tap on the phone
Plug in the cable, adb push five payloadsThe App deploys them automatically
adb shell sh kp_arm.sh to arm the kprobeAutomatically armed and verified
adb shell -tt ./pk64560 --runptyrun allocates a pty and then runs it
Manually type ksud commands into the root shellAutomatically injected after capturing ROOT_CHILD_HOLD_PASS
su -c id to verifyAutomatically verified and the result displayed

What it gives you: su -c id returns uid=0(root) ... context=u:r:ksu:s0, and the KernelSU manager shows "Working".

What this is not

  • ❌ Not persistent root. It's gone on reboot, and it doesn't write to the boot partition.
  • ❌ Does not support other models. The code has strict model/fingerprint checks; if the fingerprint doesn't match, it fails and exits immediately. This isn't being conservative, it's a hazard: the kernel addresses, struct offsets, and slab parameters were all measured on this exact kernel version, and a different version would directly corrupt the kernel.
  • ❌ Not Magisk. No module system, no hiding, no auto-start on boot.
  • ❌ Not guaranteed to succeed on the first try. In testing, there's about a 40% chance of a kernel panic and reboot; just start over after the reboot.

Supported devices

Only this one device, two OS versions:

机型        REDMI K90 Max (2604FRK1EC)
代号        prague
内核        6.12.69-android16-6-g586bfab1b9c5-abogki536749445-4k
系统        澎湃 OS 4.0.0.14.XAACNXM     ← 真机实测通过(2026-10-25)
            OS4.0.5.0.XAACNXM           ← 真机实测通过(2026-11-05)
指纹        Redmi/prague/prague:17/CP2A.260605.016/OS4.0.0.14.XAACNXM:user/release-keys
            Redmi/prague/prague:17/CP2A.260605.016/OS4.0.5.0.XAACNXM:user/release-keys
            Redmi/prague/prague:17/CP2A.260605.016/17OS4.0.261020.233332783.MTPECN.S:user/release-keys
安全补丁     2026-09-01 / 2026-10-01

Why 4.0.5.0 also works: That OTA did not recompile the kernel. Extracting the boot partition from the 8.96 GB full payload and decompressing it with LZ4 yields an Image whose version string, build time, and ABO build id are completely identical to 4.0.0.14, and the upstream fix for CVE-2026-64560 (920f893f) is not included. Address-by-address disassembly verification confirmed that all 9 hardcoded offsets match. 2026-11-05: verified working on a real device (OS4.0.5.0.XAACNXM): the first stage0 attempt panicked and rebooted, the second succeeded, and su -c id returned uid=0 context=u:r:ksu:s0.

Note: The OTA's META-INF/com/android/metadata lists post-build as the pre-release string 17OS4.0.261020.233332783.MTPECN.S, but after installation on a real device getprop ro.build.fingerprint reports OS4.0.5.0.XAACNXM. v1.0.4 only recognizes the former and will be rejected by the gate on the official release; v1.0.5 recognizes both strings.

The criterion is uname -r and the ABO build id, not the system version number. Once the kernel changes, all hardcoded offsets become invalid, and the failure mode may be a kernel panic rather than a graceful error.


Prerequisites

  1. Shizuku installed and running

    • Download the official version from RikkaApps/Shizuku (do not use the various "optimized" or "built-in adb" versions; fake packages have been observed in practice)
    • Start the service via adb or wireless debugging
    • Authorize this App
    • Third-party implementations are also supported; see "Compatible Shizuku implementations" below
  2. A kernel manager installed: SukiSU Ultra or KernelSU, pick one

    • SukiSU Ultra (preferred) or tiann/KernelSU
    • It does not need to be in a "working" state right now; it only needs to be installed — the App extracts ksud from its APK
    • Installing both is fine; the App picks the first usable one in the order SukiSU → KernelSU. To specify which one to use, tap the "Manager" row on the main screen to switch
    • ⚠️ ksud and the kernel module must come from the same manager: late-load loads the ko bundled with ksud. Mixing them causes a uapi mismatch, and the manager keeps reporting "kernel update required"
    • After switching manager branches, you must reboot first before tapping the button; otherwise the old module is still in the kernel and the new ko will fail to load due to the duplicate module name kernelsu (File exists)
  3. Keep these files on the device (if you have run it manually before)

    • /data/local/tmp/kernelsu-prague.ko.disabled — must be renamed, otherwise the exploit will load that old module with uapi=2, and the manager will report "kernel update required"

Usage

First time

  1. Start Shizuku (see the next section) and confirm the App status line shows Shizuku: 已就绪
  2. (Optional) Tap the Manager row to confirm which manager to use. The default "Auto" = SukiSU → KernelSU, first usable one; when both are installed, it is recommended to select one manually to avoid a mismatch with the module already loaded in the kernel
  3. Tap 开启 root
  4. Read the risk notice and tap 我已知晓风险,继续
  5. Wait 3–8 minutes. Do not exit the App during this time

Signs of success: the status line changes to root: 已开启 ✅ and 模块: kernelsu 已加载, and the log shows === 成功: su 已可用 ===.

Verifying afterwards

adb shell su -c id
# uid=0(root) gid=0(root) groups=0(root) context=u:r:ksu:s0

Disable root

Tap Disable root (reboot). This is the only reliable way — stage0 has modified the kernel's random_table, so a hot recovery is not possible.


Must do after every reboot: start Shizuku

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →