Redmi K50 Pro (matisse / MT6983 / kernel 5.10.209): uid=0 exploit + KernelSU LKM late-load on a locked bootloader. Full source, offsets, build recipe and write-up.
# matisse-public — Redmi K50 Pro (MT6983) / kernel 5.10.209 Privilege Escalation and KernelSU Loading Record
> **English TL;DR** — A fully documented, from-scratch writeup + toolkit for obtaining `uid=0` with a
> kernel SID on a **Redmi K50 Pro (matisse, MediaTek MT6983, kernel 5.10.209)** and loading **KernelSU via
> LKM late-load**, without unlocking the bootloader. Full source is published on purpose: a root tool you
> cannot audit is a root tool you should not trust.
---
## Why Full Source Disclosure
This repository does **privilege escalation**. Any closed-source tool claiming to "give you root" should be
questioned: it could equally be doing other things behind the scenes, and you cannot verify. Therefore we
**proactively publish all source code, log formats, failure cases, and reproduction steps**, including:
- Complete exploit source code (`payload_src/`) — you can read line-by-line, compile yourself, compare hashes
- All scripts and criteria (`tools/`, `ksu_persist.sh`) — including **the failed attempts**
- Actual kernel panic excerpts (`evidence/`) — proving the crashes we encountered and their root causes
- Build recipes and artifact hashes (`payload_src/mt87_build/BUILD_INFO.txt`, `SHA256SUMS`) — for you to verify
- Clear **scope boundaries and disclaimer** (see below)
**Does not contain**: any device identifiers (serial numbers / MACs), personal data. Third-party derived code sources and licenses are **listed item-by-item in [`NOTICE.md`](NOTICE.md) and [`payload_src/PROVENANCE.md`](payload_src/PROVENANCE.md)**.
---
## Results (Verifiable)
| Item | Evidence |
|---|---|
| `uid=0` | `su -c id` → `uid=0(root) gid=0(root) groups=0(root)` |
| **kernel SID** | Same line: `context=u:r:ksu:s0` |
| **KernelSU loaded** | `/proc/modules` → `kernelsu … - Live` |
| Loader logs | `/data/local/tmp/ksu_go.log` → `uid=0` / `load_policy rc=0` / `late-load rc=0` / `modules: 1` |
| Device did not crash | Same `boot_id` throughout, `uptime` increases continuously |
Complete battle report: [WIN_20261003_1620_uid0_kernelsu.md](WIN_20261003_1620_uid0_kernelsu.md)
> **Verification**: Hashes of published artifacts in this repository are in [`SHA256SUMS`](SHA256SUMS); build recipes and expected sha256 for exploit artifacts are in
> [`payload_src/mt87_build/BUILD_INFO.txt`](payload_src/mt87_build/BUILD_INFO.txt). If you don't trust any binary, use only source code to compile yourself.
---
## What It Does (High Level)
1. **Round R**: Heap layout on `pselect`'s `fd_set`, combined with dangling `pi_blocked_on` after `rt_waiter` release
to trigger `rt_mutex_adjust_prio_chain` walk, landing on a controlled write (write to `task->real_cred`).
2. **Round E5**: Zero out SELinux's enforcing flag (Per-Android `enforcing-8` write), enter Permissive mode.
3. **Round C**: Write `task->cred` (actual uid=0 + kernel SID).
4. **gate branch** (this repository's key patch): At the moment of **actually obtaining uid=0**,
`system("sh /data/local/tmp/ksu_go.sh &")` — use the official userspace loader to...