Explore >> Select a destination
|
You are here 
|
xenophanes.net | ||
| | | | |
debugging.works
|
|
| | | | | describes how to debug a Linux Kernel Module | |
| | | | |
albocoder.github.io
|
|
| | | | | [AI summary] This blog post details the process of using static analysis with LLVM bitcode to identify the slab cache for kernel objects in the Linux kernel. | |
| | | | |
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. | |
| | | | |
klecko.github.io
|
|
| | | Last month Blue Frost Security published two exploitation challenges for Ekoparty 2022. One of them was a Linux kernel challenge. I don't have much experience with Linux kernel exploitation, so this was a good opportunity to practise. I also write this up as a reference for my future self. | ||
