kernelXDK

kernelXDK: Streamlining Kernel Exploit Development

kernelXDK is an open-source library designed to significantly streamline kernel exploit development. It addresses common challenges in this domain by reducing repetitive tasks, fostering exploit universality across Linux distributions, and enhancing exploit readability.

Key Features and Benefits

• Eliminates Tedious Maintenance: kernelXDK removes the burden of maintaining version-specific offsets and gadgets across different Linux releases, a task often found tedious by developers.

• Enhances Focus on Innovation: By abstracting away mundane tasks, the library allows developers to concentrate on the more challenging and innovative aspects of kernel exploitation.

• Universal Exploit Compatibility: It enables the creation of universal exploits that function seamlessly across various Linux flavors.

• Improved Readability: The library’s design promotes improved exploit readability, making the code easier to understand and maintain.

• Designed for Broad Support: kernelXDK is engineered with the capability to support a wide range of kernel exploitation scenarios and environments.

About

• Introduction
  • Rationale behind the kernelXDK
  • Limitations
• What is kernelXDK?
  • Tools
  • Future ambitions
• KXDB Database
  • Database concept
  • KXDB file format
  • Contents
  • kernelCTF KXDB distribution

libxdk

• What is libxdk?
  • Planned Features
• Installation
  • Binary release
  • Source code compilation
  • Tests
• How to get started
  • Initialize the Target Database
  • Building the Payload
  • Assembling the Final Payload with PayloadBuilder
• How to port an existing exploit
  • Introduction
  • Includes
  • Hardcoded sizes and offsets
  • Everything ROP related
• API Reference
  • XDK Device Module
  • RIP Module
  • Target Module
  • Utility Module
  • Pivot Module
  • Payloads Module

Command Line Tools

• Kernel Image DB
• Kernel Image Runner
• KXDB Tool
• Kernel ROP Generator

Note

This documentation is still under active development. If you find any issues or have suggestions, please open an issue on our GitHub repository.