
SM-F9360 (Galaxy Z Fold4, q4q) locked-bootloader KernelSU root — CVE-2026-43499 temp root → LD_PRELOAD DEFEX bypass → no-LTO clang-12 kernelsu.ko. Device-verified 2026-08-12.
CVE-2026-43499 temporary root → LD_PRELOAD channel bypasses DEFEX → non-LTO clang-12 build of kernelsu.ko → full su + KernelSU Manager functionality
Status: ✅ Verified on real device on 2026-08-12 (firmware
F9360ZCSAIZF1, kernel5.10.236-android12-9-2755199-abF9360ZCSAIZF1)✅ Added 2026-10-28:
F9360ZCSAIZH2(build 2026-08-18) ported and re-verified on real device — this firmware does not fix CVE-2026-43499; you only need to shift the three data symbol offsets by +0x380 (see §11).This project documents a complete, reproducible process for achieving KernelSU root on a Samsung device with a locked Bootloader: no BL unlock, no boot.img flashing, no Odin required.
TL;DR (English): This repo documents a fully device-verified jailbreak path for a locked-bootloader Samsung Galaxy Z Fold4 (SM-F9360, SM8450, kernel 5.10.236, firmware F9360ZCSAIZF1): a CVE-2026-43499 (rtmutex UAF, fixed in July-2026 firmware) exploit chain grants temporary kernel-domain root; a custom LD_PRELOAD constructor .so bypasses Samsung's DEFEX execve interceptor to init_module() a KernelSU LKM built with the exact device toolchain (AOSP clang 12.0.5 r416183b) and with LTO disabled — the two factors that make the module loadable and its init executable on this CFI/LTO hardened kernel. Result: su works (uid=0, context=u:r:ksu:s0) and KernelSU Manager v3.2.5 recognizes the kernel. Root is in-memory only: every reboot requires re-running the exploit (~3 min, scripted). All pitfalls and dead ends (fake exports, CRC patching, ksud late-load, LTO function-sections layout) are documented below.
| Item | Status |
|---|---|
Temporary root (kernel domain kernel:s0) | ✅ Achieved reliably (9 consecutive successes) |
KernelSU module loading (init_module) | ✅ kernelsu ... Live (O) |
| Full KSU init execution | ✅ All 15 instrumentation marks green |
su command | ✅ uid=0(root) gid=0(root) context=u:r:ksu:s0 |
| KernelSU Manager v3.2.5 | ✅ Recognizes kernel version (supercall detection passes), works under SELinux enforcing mode |
| Bootloader unlock | ❌ Not required |
| Flashing/modifying partitions | ❌ Not required |
Essential limitation: BL lock → root is a pure in-memory state. After every reboot, the exploit must be re-run and the modules reloaded (the whole process takes about 3 minutes and has been scripted). The ksud userspace daemon cannot be deployed (DEFEX blocks execve, see §10-4), but su / supercall / Manager are all handled directly by the kernel sucompat and do not depend on ksud.
Warning: rmmod kernelsu will cause the device to immediately panic and reboot (the syscall-table restoration path on RKP-protected memory)—never unload it.
fastboot oem unlock does not exist; any persistent root (magisk/kernel patch) requires flashing boot.img, and a locked BL rejects all self-signed images.CONFIG_CFI_CLANG=y + Full LTO. The only source of mod->init is the CFI jump-table slot __cfi_jt_init_module; indirect calls must go through a .cfi_jt table entry, otherwise the CFI check panics immediately.__ksymtab export table, so a normal insmod cannot resolve them (Unknown symbol).IGNORE_MODVERSIONS/IGNORE_VERMAGIC flags all lead to the dead end of try_to_force_load().sarabpal-dev/IonStack-S22U (b0q / S22U, exp32 route).LD_PRELOAD constructor .so is the only exempt channel for executing arbitrary code in the root domain.ksud late-load) is designed precisely for bootloader-locked devices: no boot image flashing, just runtime init_module.┌─ Layer 1: CVE-2026-43499 临时 root
│ ionstack-q4q exploit(KASLR 泄漏 → mm reclaim → exp32 32-bit 栈 stamp
│ → CFI r/w → pipe physrw → UMH root daemon)
│ → /data/local/tmp/cve-2026-43499-root -c '<cmd>' = kernel:s0 域 root 命令通道
│
├─ Layer 2: LD_PRELOAD .so 加载通道(DEFEX 绕过)
│ DEFEX 拦截 kernel 域 execve 任何新 ELF(Killed);LD_PRELOAD 的 constructor
│ 执行豁免 → ksu-load.so 在 /system/bin/true 进程内:
│ 读 ko → /proc/kallsyms 手工重定位 201 个 UND 符号(SHN_ABS + st_value=绝对地址)
│ → vermagic patch(旧版需要)→ init_module() → 成功
│
└─ Layer 3: KernelSU 内核模块(无 LTO clang-12 版)
init 完整执行 15 mark 全绿 → sucompat (allow_shell=1) + supercall 可用
| Item | Value |
|---|---|
| Model | SM-F9360 (Galaxy Z Fold4, q4q) |
| SoC | SM8450 (Snapdragon 8+ Gen 1) |
| Firmware | F9360ZCSAIZF1 (≤ 2026-06 build, contains CVE) |
| Kernel | 5.10.236-android12-9-2755199-abF9360ZCSAIZF1 |
| Device compiler | AOSP clang 12.0.5 (r416183b, c935d99d7cf) (confirmed by /proc/version) |
| Exact vermagic | 5.10.236-android12-9-2755199-abF9360ZCSAIZF1 SMP preempt mod_unload modversions aarch64 |
Different firmware = different kallsyms / layout / vermagic, requiring re-adaptation of target.h and recompilation. See §11.
clang-14/15 + focal repo clang-12 / lld-12 (/usr/bin/clang-12, /usr/bin/ld.lld-12)CC=clang HOSTCC=clang LD=ld.lld-12FryUpDoe/android_kernel_samsung_q4q (opensource.samsung.com has Cloudflare anti-scraping)