CVE-2017-11176: A step-by-step Linux Kernel exploitation
In Summary : This series covers a step-by-step walkthrough to develop a Linux kernel exploit from a CVE description. It starts with the p...
https://updatesinfosec.blogspot.com/2018/10/cve-2017-11176-step-by-step-linux.html
In Summary :
This series covers a step-by-step walkthrough to develop a Linux kernel exploit from a CVE description. It starts with the patch analysis to understand the bug and trigger it from kernel land (part 1), then it gradually builds a working proof-of-concept code (part 2). The PoC is then turned into an arbitrary call primitive (part 3) which is finally used to execute arbitrary code in ring-0 (part 4).
The targeted audience is the Linux kernel newcomers (nothing too fancy for the veterans). Since most kernel exploit articles imply that the reader is already familiar with the kernel code, we will try to fill the gap by exposing core data structure and important code paths. In the end, every single line of the exploit should be understood, as well as their impact on the kernel.
While it is impossible to cover everything in a single article, we will try to unroll every kernel path needed to develop the exploit. Think of it as a guided Linux kernel tour supported by a practical example. Exploit writing is actually a good way to understand the Linux kernel. In addition, we will show some debugging techniques, tools, common pitfalls and how to fix them. [...]
kindly refer the following link as follow up :
https://ift.tt/2IwS9Gd
This series covers a step-by-step walkthrough to develop a Linux kernel exploit from a CVE description. It starts with the patch analysis to understand the bug and trigger it from kernel land (part 1), then it gradually builds a working proof-of-concept code (part 2). The PoC is then turned into an arbitrary call primitive (part 3) which is finally used to execute arbitrary code in ring-0 (part 4).
The targeted audience is the Linux kernel newcomers (nothing too fancy for the veterans). Since most kernel exploit articles imply that the reader is already familiar with the kernel code, we will try to fill the gap by exposing core data structure and important code paths. In the end, every single line of the exploit should be understood, as well as their impact on the kernel.
While it is impossible to cover everything in a single article, we will try to unroll every kernel path needed to develop the exploit. Think of it as a guided Linux kernel tour supported by a practical example. Exploit writing is actually a good way to understand the Linux kernel. In addition, we will show some debugging techniques, tools, common pitfalls and how to fix them. [...]
kindly refer the following link as follow up :
https://ift.tt/2IwS9Gd
