Explore >> Select a destination
|
You are here 
|
pwning.systems | ||
| | | | |
xcellerator.github.io
|
|
| | | | | In all the playing around I've been doing with Linux kernel modules, I decided to see what would happen if you tried to load one from a Docker container. It turns out that privileged containers (or just those with CAP_SYS_MODULE) are able to use the sys_init_module() and sys_finit_module() syscalls - which are what's used to load kernel modules. As all containers share their kernel with the host (unlike VMs), this clearly results in yet another complete system compromise. | |
| | | | |
xenophanes.net
|
|
| | | | | [AI summary] The provided text is a detailed guide on creating a Linux kernel module that implements a character device with ioctl functionality. It walks through the process of setting up the module, defining the device structure, implementing open and release functions, adding ioctl support for adding two integers, and includes test code for user-space interaction. The guide also mentions additional resources for learning about Linux device drivers. | |
| | | | |
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. | |
| | | | |
tthtlc.wordpress.com
|
|
| | | How to use QEMU to run a VM client, assuming that the kernel have kvm enabled and running? a. create rootfs image as your OS file image, with all the general GNU/Linux utilities: This is how I create the rootfs for Xenial (I copied and modified from Syzkaller project), using the debootstrap command mainly, but... | ||
