linux-kernel-so-injector

KO | EN

gitlite — search

#python #hacktoberfest #react #llm #android #machine-learning #rust #linux #docker #java #cli #vue #mcp #open-source

linux-kernel-so-injector

(★ 96)

Kernel mode to user mode so injection

linux-kernel-so-injector 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# linux-kernel-so-injector
## TL;DR
Linux kernel mode to user mode so injection

Tested on linux kernel version: 4.19.91. Current version depends on libc, but it's easy to change it.

Inject shared library to target process from the kernel

## How it works
The injection process is divided into several stages:

1. Send SIGSTOP to target process
2. Find free space for our shellcode (any R^X pages) using /proc/PID/maps
3. Find libc address using /proc/PID/maps
4. Parse libc elf at runtime to find __libc_dlopen_mode
5. Get the target process rip register 
6. Build our shellcode (get_shellcode function) with the correct address of:
    * So file path
    * Previous rip register address (in order to reconsturct the running of the process after loading the so from our shellcode)
    * __libc_dlopen_mode address (using this function in libc, we will load our so)
7. Write to target process memory the so file path
8. Write the shellcode to target process memory
9. Set target process rip register to the shellcode address
10. Send SIGCONT to target process

The whole process described above happens at the kernel module.
The only things that the kernel module needs are: target pid, so file path.

## Limitations
* Currently there is no support for syscalls from the type that need EINTR or restart_syscall when stopped by signal.
* Currently implemented only for x86_64.
* This code isn't robust or fully tested. Therefore, you should expect bugs to occur under certain conditions when process getting non-stop signals or other edge cases.
* The shellcode and so path won't cleaned because I didn't have enough time to implement it from different kernel thread, but there is a commit which all the cleanup code available. However, the kernel thread isn't and without the creation of new kernel thread it will stick the injection.
* The reconstruction isn't fully (r15 isn't restored).

All of the limitations which mentioned above could be solved.

linux-kernel-so-injector

linux-kernel-so-injector 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

linux-kernel-so-injector

linux-kernel-so-injector 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README