GhostLock
1.2 · GitHub
More about this app
One-tap CVE-2026-43499 privilege-escalation app granting temporary uid 0 across many stock devices; Shizuku-required kernel profiles run through a shell Shizuku.
GhostLock-App
GhostLock uses CVE-2026-43499 to gain temporary root on supported Android kernels and load KernelSU.
Use the app
- Install a root manager APK from KernelSU, SukiSU Ultra, BakaSU/ReSukiSU, or KowSU.
- Install the GhostLock APK and open it.
- Check that your kernel is supported, then tap Run.
Support requires an exact uname -r match. Check the supported devices for your kernel build.
If Shizuku is enabled, start it with ADB before running GhostLock. Tap GhostLock's status card to grant access.
Any root manager that ships libksud.so provides ksud for module loading. The built-in list (KernelSU, SukiSU Ultra, ReSukiSU, BakaSU, KowSU) is auto-detected, and other managers can be picked in Settings → Root manager. Without ksud, W1/W2 still grant uid 0 but no module is loaded.
Add a kernel profile
You can import a profile without rebuilding the app:
- Parse OTA link accepts a full OTA ZIP URL.
- Parse local image accepts
boot.imgand an optionalxbl_config.img. - Import offsets.conf (v2) accepts a HOCON profile. Import offsets.json (v1) converts an older JSON report in the app.
Extractor output is an unverified candidate. The app checks missing or invalid fields before execution. Generating a profile does not prove device support. See the porting guide for validation and built-in registration.
See the MediaTek guide for image-based address recovery and the rooted-device fallback.
Command-line tools
Run the native binary with an exported profile
Requires the Android NDK, make, Gradle, and ADB. An adb shell run skips the app's seccomp bypass stage.
make -C src ghostlock
./gradlew exportKernelProfiles
adb push build/native/ghostlock /data/local/tmp/ghostlock
adb push "build/kernel-profiles/<release>.bin" /data/local/tmp/profile.bin
adb shell chmod 755 /data/local/tmp/ghostlock
adb shell /data/local/tmp/ghostlock --load-prebuilt-profile /data/local/tmp/profile.bin
Build and run the offset extractor
Requires Rust. The extractor accepts a boot image, a full OTA ZIP, or an HTTP(S) URL.
(cd tools/extract_rs && cargo build --release)
build/extract/release/ghostlock-extract boot.img --xbl-config xbl_config.img --format conf --out profile.conf
build/extract/release/ghostlock-extract OTA.zip --format conf --out profile.conf
Import profile.conf in the app. Omit --xbl-config if you do not have that image. The extractor rejects a patched remove_waiter() with exit code 6.
Reference
- Profile schema and execution defaults
- Native core
- Add a component, engineering rules, and writing rules
Credits and license
Licensed under Apache License 2.0. Based on:
How Shizuku is used
Can run one-tap kernel privilege escalation via `Shizuku user service`.
This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.
How this app uses Shizuku
Shizuku is used to run the one-tap privilege escalation with shell identity so the exploit can succeed where the normal app identity cannot.
- Run privilege escalation: tapping Run with the Shizuku option starts the bundled native exploit inside the Shizuku service (shell identity without seccomp filtering) using the selected CPU pair, safety mode choice, force attack test flag and the matched kernel profile for the running kernel, then shows its log and completion status in the app.
Android APIs or commands used
android.os.Process.myUidandroid.os.Process.SHELL_UID
Notable details
The same Run action also offers a base mode without Shizuku that runs the same exploit with the normal app identity. The Shizuku run requires a matching kernel profile for the running kernel, otherwise it stops with a profile unavailable message.
Changelog
What's new for version 1.2
GhostLock Pre-release
- Version:
v1.2(594) - Commit:
72822138
Commit Message
profiles: add 6.6.89-android15-8-g6bf8136549d7-abogki463261049-4k (iQOO 13) (#887)
Adds the builtin profile for iQOO 13 (V2408A / PD2408) on
PD2408D_A_16.1.10.20.W10.V000L1, kernel
6.6.89-android15-8-g6bf8136549d7-abogki463261049-4k.
Generated with tools/extract_rs from the matching full OTA zip
(9,525,618,558 bytes; payload FILE_HASH verified) rather than boot.img
alone, so xbl_config/uefi were available and kernel_phys_load resolved
to 2818572288 (0xA8000000).
Verified on the real device with Shizuku: pselect route done success=1,
SELinux permissive, vr.ko bypassed, KernelSU v3.3.1 reports
"Working [Jailbreak mode]".
Files
GhostLock-release.apk: GhostLock Android Applicationghostlock: Standalone GhostLock native binary (Android arm64-v8a)GhostLock-kernel-profiles.zip: Bundled kernel profiles (HOCON)ghostlock-extract-android-arm64: Kernel offset extractor CLI (Android arm64-v8a)ghostlock-extract-linux-x86_64: Kernel offset extractor CLI (Linux x86_64)ghostlock-extract-macos-universal: Kernel offset extractor CLI (macOS Universal arm64 + x86_64)ghostlock-extract-windows-x86_64.exe: Kernel offset extractor CLI (Windows x86_64)
SHA256 Checksums
24a082ddd0454fd8c7669024ca2dde52a854eb520a85378918eaca280001e344 GhostLock-release.apk
c2112f1ffcd29a886df2280a7a457618c4429e641be9d61693fb677c46f48219 ghostlock
3fc007a084b4f41bebf1e4190ac06edea06ffc44893694d5559f2af8571c5b60 ghostlock-extract-android-arm64
57b663b93a84722e36312c71529ebb80421c6d8a6b9ea9be7f22c357ba1d648c ghostlock-extract-linux-x86_64
bed106df63c44185235746dae87871a7c073a5ad48852b0d3579a34b2841ec49 ghostlock-extract-macos-universal
c390816523488dd33479698a595f80e78337180891d86b432dff7657389e0020 ghostlock-extract-windows-x86_64.exe
81144c0ca15383d990e47974f1afeeaaa9c6888ce23aa3a68b2fd590687a30e8 GhostLock-kernel-profiles.zip
Permissions
4 permissions requested
Sources
2 sources
Sources
2 sources