Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2022-20409 PoC — Google Pixel 资源管理错误漏洞

Source
Associated Vulnerability
Title:Google Pixel 资源管理错误漏洞 (CVE-2022-20409)
Description:In io_identity_cow of io_uring.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-238177383References: Upstream kernel
Description
Android kernel exploitation for CVE-2022-20409
Readme
# Bad IO_uring

https://www.blackhat.com/us-23/briefings/schedule/index.html#bad-io_uring-a-new-era-of-rooting-for-android-32243

## Build the exploit

Make sure the [Android NDK](https://developer.android.com/ndk) is installed. For pixel 6,
```bash
make pixel
```

For samsung s22,
```bash
make s22
```

## How to use the exploit
The exploit is written to support different versions of kernels. In order to port the exploit to a different kernel, you need to extract the symbol file of the target kernel.

The kernel could be extract from the factory image of the phone. For Pixels, download the factory image [here](https://developers.google.com/android/images).

After downloading the image, extract the image to get `boot.img` file. `boot.img` can be extracted with `tools/unpack_bootimg.py`.
```bash
python3 tools/unpack_bootimg.py --boot_img boot.img --out out
```
You will see the kernel at `out/kernel`


Now, with the kernel image, we can use [vmlinux-to-elf](https://github.com/marin-m/vmlinux-to-elf) to extract kernel symbols from it.
```
./tools/vmlinux-to-elf/kallsyms-finder out/kernel > pixel.kallsyms
```

You have to make sure the `Version string` extracted in the symbol matches your phone's kernel version. The kernel version of the phone could be looked up through `adb`. For example,

```
sh-3.2$ adb shell
oriole:/ $ uname -a
Linux localhost 5.10.66-android12-9-00007-g66c74c58ab38-ab8262750 #1 SMP PREEMPT Mon Mar 7 01:27:36 UTC 2022 aarch64
```
matches 
```
[+] Version string: Linux version 5.10.66-android12-9-00007-g66c74c58ab38-ab8262750 (build-user@build-host) (Android (7284624, based on r416183b) clang version 12.0.5 (https://android.googlesource.com/toolchain/llvm-project c935d99d7cf2016289302412d708641d52d2f7ee), LLD 12.0.5 (/buildbot/src/android/llvm-toolchain/out/llvm-project/lld c935d99d7cf2016289302412d708641d52d2f7ee)) #1 SMP PREEMPT Mon Mar 7 01:27:36 UTC 2022
```

Now you can push the exploit and the symbol file to the phone and get it rooted with the following commands.

```bash
make
adb push exp pixel.kallsyms /data/local/tmp
adb shell
cd /data/local/tmp
./exp pixel.kallsyms
```

Enjoy your root shell :)
File Snapshot

[4.0K] /data/pocs/b546c71e4561d50025639732aceeac5061b15ced ├── [ 183] Android_pixel6.mk ├── [ 180] Android_s22.mk ├── [ 29K] exp_pixel6.c ├── [ 32K] exp_s22.c ├── [ 624] Makefile ├── [5.9M] pixel.kallsyms ├── [2.1K] README.md ├── [4.4M] samsung.kallsyms └── [4.0K] tools ├── [ 22K] unpack_bootimg.py └── [4.0K] vmlinux-to-elf ├── [ 33] kallsyms-finder -> vmlinux_to_elf/kallsyms_finder.py ├── [ 34K] LICENSE ├── [4.0K] pics │   └── [ 52K] landing_illustration.png ├── [9.1K] README.md ├── [ 589] setup.py ├── [ 22] vmlinux-to-elf -> vmlinux_to_elf/main.py └── [4.0K] vmlinux_to_elf ├── [6.8K] architecture_detecter.py ├── [8.6K] elf_symbolizer.py ├── [ 0] __init__.py ├── [ 42K] kallsyms_finder.py ├── [3.1K] main.py ├── [2.1K] tests.py ├── [4.0K] utils │   ├── [ 35K] elf.py │   ├── [4.0K] elf_tests │   │   ├── [148K] ls_arm32_le.elf │   │   ├── [392K] ls_mips32_be.elf │   │   ├── [302K] ls_mips32_le.elf │   │   ├── [400K] ls_mips64_be.elf │   │   ├── [532K] ls_renesas.elf │   │   ├── [131K] ls_x64.elf │   │   └── [414K] x86_shared_library.so │   ├── [ 0] __init__.py │   ├── [1.5K] lz4_legacy.py │   └── [3.6K] pretty_print.py └── [ 12K] vmlinuz_decompressor.py 6 directories, 33 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →