项目的 README,来自 github.com/mitschud/DirtyFrag。合并为一个 markdown 文件:README.md。
Root without unlocking. Gone after reboot.
An ephemeral Android root utility powered by CVE-2026-43284.
Built for Samsung devices, with a One UI-inspired interface, KernelSU integration,
and no custom kernel or unlocked bootloader required on vulnerable devices.
[!IMPORTANT] Compatibility depends on the device's kernel and security patches. Root is ephemeral. The kernel module,
suand any loaded modules are gone the moment the device reboots. A reboot always returns the phone to a clean, unrooted state - which is also the recovery path if a run goes wrong.
libksud.so:[!WARNING] Since 1.10 (upstream 3.2) DirtyFrag no longer bundles
ksud- it is staged from the selected manager's ownlibksud.so. A manager that does not ship that library cannot give you root. The older advice to install a CI / Actions build of the manager no longer applies.
[!NOTE] Pre-release builds of
masterare not published to Releases. Take theDFRootartifact of the latest green Build run: it is a signed release build - the workflow restores theKEYSTOREsecret intoapp/keystore.jksand runsassembleRelease- and inside the artifact the APK is atapp/build/outputs/apk/release/dirtyfrag.apk. Tagged and untagged builds go through that same keystore step, so amasterbuild carries the released app's signing key and installs over it as an update rather than a fresh install.
A fresh install of DirtyFrag gets a new Android UID, so the grant in the manager has to be given again after every reinstall.
dfroot.ko is unloaded after late-load and ksud's own soft-reboot is runSimplified Chinese sits above English (Samsung: Settings > System > Languages, drag it up). One
UI 9 has no per-app switch, so that list is the only lever. The advanced log translates at display
only: the screen reads Chinese, the file saveLog() writes stays EnglishQ: Log says patching failed and that my device isn't vulnerable
A: Sorry, there is no fix. Either:
Q: Log says "SUCCESS" or "ksud exited with error", but I don't have root
A: Turn off Auto reboot on the Autorun card if it is enabled - a soft reboot that the manager cannot complete leaves the loaded module unloaded again. Otherwise see upstream discussion 69.
Q: I installed a module and now I can't launch root without crashing
A: Set the KernelSU Modules card to Disabled and reroot. The switch works without root, which is the point - it is the escape hatch when a module is the thing that is crashing the run.
Q: Module + Autorun and now I am bootlooping
A: Android usually detects the bootloop and offers Safe Mode; otherwise hold Volume Down during
boot. From Safe Mode turn Autorun off and set KernelSU Modules to Disabled, or just uninstall
DirtyFrag until you stabilise. If you cannot get far enough into the system, adb uninstall df.root
from any PC works on user builds without root.
Q: The progress bar sits at 0 percent
A: That is the app's log-marker mapping, not the exploit. The run window is 70 seconds - do not re-run a "slow" run, the daemon may still be working.
Q: How do I remove root cleanly?
A: Before unrooting, use file manager with root and delete /data/adb/ksu, ksud, module residue.
JAVA_HOME="<Android Studio jbr>" ./gradlew assembleRelease
The APK is written to app/build/outputs/apk/release/dirtyfrag.apk.
Release builds are signed with app/keystore.jks, which is gitignored (the signing config expects
alias dirtyfrag and dirtyfrag for both passwords). Generate your own before building:
keytool -genkeypair -v -keystore app/keystore.jks -alias dirtyfrag \
-keyalg RSA -keysize 2048 -validity 10000 \
-storepass dirtyfrag -keypass dirtyfrag
The eight prebuilt kernel modules are committed under app/src/main/jni/ko/. Upstream gitignores
them and builds them per-KMI in CI; this fork commits them so a plain clone builds without a DDK
toolchain. They are built by this repo's Build workflow (the LKMs / <kmi> jobs) from the
current lkm/dfroot.c, so they must be rebuilt whenever that file changes: run the workflow,
download the df-lkm-<kmi> artifacts and drop them in this directory. To build them yourself
instead, use upstream's make / podman DDK flow.
The Android kernel decrypts AES-CBC ESP packets directly into the page cache of files open for
splice(). By crafting IV = AES_ECB_DEC(key, current_content) XOR desired_content, any
16-byte-aligned block in a mapped shared library can be overwritten without write permission and
without copy-on-write.
The exploit uses this primitive to patch shellcode into libc++.so in the kernel's page cache. The
next privileged call to the hooked function runs the shellcode, which loads the kernel module via
insmod.
UdpEncapsulationSocket plus an SPI and builds an
AES-CBC/HMAC-SHA256 ESP transform through IpSecManager.crash_dump64 using the CBC
primitive. crash_dump64 runs in the crash_dump SELinux domain, which can open vendor_file
labelled files that untrusted_app cannot read - the bridge we need.vendor_file-labelled file.std::ostream::sentry::sentry(). It checks uid and tid, creates /dev/df as a one-shot mutex so
it cannot re-enter, then execs insmod in the vendor_modprobe domain.call_usermodehelper to run the bootstrap.GPL-2.0-only - the full text is in LICENSE, the file upstream added in 4ec133c because
the upstream maintainer asked for one. Upstream keeps its own copyright on its code; everything this
fork adds on top of it is licensed under the same GPL-2.0-only, from the 1.17 merge onward.
That single licence has one consequence worth stating before anyone ports code in: GPL-2.0-only cannot absorb GPL-3.0-only code. A GPL-3 reference - the Samsung download-mode (Odin) work, for example - may be read for behaviour, record formats and API naming, and none of its code may be copied, translated or linked into this tree. The same rule is written down in docs/d2-download-mode-writer.md.