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
ghostlock-kit — One-click root kit for vivo iQOO Neo9S Pro (MT6989) exploiting CVE-2026-43499 futex PI UAF via MCAST transport, with scripts and analysis docs. | Kitploit
Tools/GitHubGitHub/zhubaohe123/ghostlock-kit
Android SecurityPrivilege EscalationExploitationMobile App PentestingPost-ExploitationMobile SecurityHardware & IoT SecurityPapers & ResearchPayload DevelopmentBinary Exploitation
GitHub
831742 months agoNot yet reviewed
Share
zhubaohe123/ghostlock-kit

ghostlock-kit

One-click root kit for vivo iQOO Neo9S Pro (MT6989) exploiting CVE-2026-43499 futex PI UAF via MCAST transport, with scripts and analysis docs.

View Repository

GhostLock Kit — vivo iQOO Neo9S Pro (V2339FA / MT6989)

GhostLock one-click root kit for the vivo iQOO Neo9S Pro (V2339FA, MediaTek MT6989). This repository contains: MCAST transport porting patch, one-click scripts, and full analysis documentation; for the complete runnable kit (including binaries and KernelSU), see Releases.

Device: vivo iQOO Neo9S Pro (V2339FA / PD2339, MT6989) Firmware: PD2339_A_16.2.12.1.W10.V000L1 (Android 16) Kernel: 6.1.145-android14-11-maybe-dirty Vulnerability: CVE-2026-43499 (futex PI requeue UAF) For device owners / security research only. Use on your own device.

Highlights (TL;DR)

  • The original GhostLock's TCP/pselect transport has misaligned stack frames on this device (vendor +pgo,+bolt kernel) and always crashes; this port discovered and switched to the 0x108-byte stack copy of setsockopt(SOL_IP, MCAST_JOIN_SOURCE_GROUP, buf, 0x108) as the poisoning primitive, fully covering the stale rt_mutex_waiter and completing the full chain (W1→W2→W3→KernelSU).
  • Measured success-rate tip: after the device reboots, stay on the lock screen and do not unlock; at this point the system has the fewest user-space services, and it almost always succeeds on the first try.
  • Uses the official KernelSU v3.3.0 paired versions (manager 32601 + driver 32601), with no version-mismatch warnings. (Measured: ReSukiSU 4.2.0-rc1 manager causes an immediate kernel freeze on this device when opened, so it has been abandoned.)

Quick Start

  1. Download ghostlock-kit-20260913.zip from Releases and extract it.
  2. Connect the phone to the computer via USB (adb already authorized).
  3. Run:
cd <extract-dir>\ghostlock-kit
powershell -ExecutionPolicy Bypass -File .\scripts\run-at-lockscreen.ps1 -Reboot
  1. When you see [+] Root succeeded!, it is done (do not unlock the phone during execution). Verify:
adb shell su -c id
# uid=0(root) gid=0(root) groups=0(root) context=u:r:ksu:s0

Failure triggers a kernel panic and automatic reboot; the script will automatically wait and retry (success rate about 25–30% per attempt; at the lock screen it almost always succeeds on the first try). root is temporary (KernelSU late-load); after the phone reboots, the script must be rerun.

Repository Structure

.
├── scripts/
│   ├── run-at-lockscreen.ps1   # One-click: reboot→wait for lock screen→push and verify→run→auto retry (recommended)
│   └── retry-if-needed.ps1     # Generic retry (does not force reboot)
├── src/
│   └── ghostlock-mcast.patch   # Source changes (baseline ghostlock-app @ 50d2b72)
├── docs/                       # Analysis documentation (exploit report/transport analysis/waiter and PI walk/device manual/troubleshooting log)
└── LICENSE                     # Apache-2.0 (inherited from upstream)

Binaries and the complete kit (files/ghostlock, files/ksud, files/offsets.json, KernelSU APK) are not placed in the git repository; please download ghostlock-kit-20260913.zip from Releases.

Release Assets and Verification

AssetDescriptionSHA-256
ghostlock-kit-20260913.zipComplete kit (scripts + binaries + APK + docs)df547f6b2852a0d86582958e049ef5a44599a5a91ce0dace2162fb7d0fcab11d

Key files in the kit (MD5):

FileMD5
files/ghostlock (exploit program)e581609ed114d33efa3b8a1958f85637
files/ksud (official KernelSU v3.3.0 user-space)de059ed8ffd896129a0a4bbe338c946a
files/offsets.json (offsets for this device)a2498197161b01bdcc5dffc0614fbfbd

Principle Overview

  • Vulnerability: CVE-2026-43499 — after the waiter thread returns from FUTEX_WAIT_REQUEUE_PI, task->pi_blocked_on still dangles, pointing to the rt_mutex_waiter on its stack.
  • Poisoning (the core of this port): setsockopt(SOL_IP, MCAST_JOIN_SOURCE_GROUP, buf, 0x108) causes do_ip_setsockopt to execute memset(0x108) + copy_from_user(0x108), and the copy range [S'−0x338, S'−0x230) fully covers the waiter (the waiter is located at buffer offset 0x60); setting buf[8]=0 makes the family check fail, and the syscall returns cleanly after the copy.
  • Trigger: consumer thread sched_setattr → rt_mutex_adjust_prio_chain reads the forged waiter → rb_erase left-only relink forms the *(target) := value write primitive.
  • Exploit chain: W1 disables SELinux → W2 child process cred = init_cred → W3 clears seccomp (skipped in the shell flow) → root script late-loads KernelSU.
  • Failure mechanism: occasional failure due to skb page reclaim race → walk crash (kernel panic and automatic reboot), which is a probabilistic event; the lock-screen state has the highest hit rate.

See docs/ for details (including evidence chain, disassembly analysis, and crash scenes).

FAQ

IssueHandling
Phone reboots after failureNormal (probabilistic event); after reboot do not unlock, just rerun the script
Manager shows "not installed/not working"First confirm su -c id works; open the manager and refresh, do not swipe it away/force stop
root disappears after rebootNormal (late-load is not persistent); rerun the script
Want to use ReSukiSUNot usable on this device (opening the manager immediately freezes and reboots); if needed, configure a matching version separately
After a system updateoffsets.json may become invalid and needs to be regenerated/imported

Build (Rebuilding from Source)

# Baseline: ghostlock-app @ 50d2b72 (includes PR#127)
git clone https://github.com/YuKongA/ghostlock-app.git
cd ghostlock-app && git checkout 50d2b72
git apply /path/to/src/ghostlock-mcast.patch
make NDK_ROOT=<your-ndk> ghostlock

Patch contents: MCAST transport (do_mcast_fake_lock_route), route selection, observe/pre-build logic, GHOSTLOCK_WALK_LOG (consumer-side walk localization), root script pstore backup, GHOSTLOCK_SKIP_VR.

Acknowledgments and License

  • Upstream project: YuKongA/ghostlock-app (Apache-2.0)
  • KernelSU (GPLv3) — the ksud and APK in this kit come from the official v3.3.0 release, and copyright belongs to their authors
  • ReSukiSU (GPLv3) — early adaptation reference
  • Changes in this repository are released under Apache-2.0 (see LICENSE)

Disclaimer

For local security research and personal root use by device owners on their own devices only; do not use on any unauthorized device or for illegal purposes. Using this tool may cause device instability or data risk; please back up on your own and bear the corresponding consequences.

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 →