/explore
|
You are here 
|
blog.osandov.com | ||
| | | | |
pwning.systems
|
|
| | | | | I'm writing this post because I often hear that kernel exploitation is intimidating or difficult to learn. As a result, I've decided to start a series of basic bugs and exercises to get you started! Prerequisites Knowledge of the Linux command line Knowing how to read and write basic C may be beneficial Being able to debug with the help of a virtual computer or another system Able to install the kernel module compilation build requirements A basic understanding of the difference between userland and kern... | |
| | | | |
sergioprado.blog
|
|
| | | | | In this article, we will learn how to debug the Linux kernel on an embedded Linux system with GDB. | |
| | | | |
xcellerator.github.io
|
|
| | | | | Okay, so you've built your first kernel module, but now you want to make it do something cool - something like altering the behaviour of the running kernel. The way we do this is by function hooking, but the question is - how do we know which functions to hook? Luckily for us, there is already a great list of potential targets: syscalls! Syscalls (or system calls) are kernel functions that can be called from userspace, and are required for almost anything remotely interesting. | |
| | | | |
hannes.robur.coop
|
|
| | | |||
