Explore >> Select a destination
|
You are here 
|
blog.frizk.net | ||
| | | | |
manybutfinite.com
|
|
| | | | | After examining the virtual address layout of a process, we turn to the kernel and its mechanisms for managing user memory. Here is gonzo again: Linux processes are implemented in the kernel as insta | |
| | | | |
github.blog
|
|
| | | | | In this post Ill exploit CVE-2022-20186, a vulnerability in the Arm Mali GPU kernel driver and use it to gain arbitrary kernel memory access from an untrusted app on a Pixel 6. This then allows me to gain root and disable SELinux. This vulnerability highlights the strong primitives that an attacker may gain by exploiting errors in the memory management code of GPU drivers. | |
| | | | |
www.internalpointers.com
|
|
| | | | | ...and the crucial role it plays in modern operating systems. | |
| | | | |
pwning.systems
|
|
| | | Following up on my first blog post, I've received a few requests to write about setting up a debugging environment; however, since everybody uses different emulators and so on, I'll mainly focus on which config options are useful! You must first obtain the kernel sources for your preferred version before you can set up a kernel suitable for debugging. We'll have to decompress it after that. # use your preferred version $ wget https://git. | ||
