> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/privesc/kernel-exploitation.md). # Kernel Exploitation Linux kernel exploit notes for local privilege escalation, Linux Exploit Suggester, Dirty COW, OverlayFS, and Ubuntu kernel CVEs. Kernel privilege escalation targets local vulnerabilities in the Linux kernel or distribution-specific patches. These exploits can be unstable, so version validation and lab testing matter before execution. ## Methodology * Identify the exact kernel, distribution, architecture, and patch level. * Use exploit suggesters as a starting point, then verify CVE applicability manually. * Compile and run proof of concept code only after confirming the target is vulnerable. ## Quick Checks ```bash uname -a cat /proc/version cat /etc/os-release lsb_release -a 2>/dev/null ``` {% hint style="info" %} Linux kernel exploitation abuses vulnerabilities in the kernel to execute code with elevated privileges. Confirm the kernel and distribution version before running a proof of concept. {% endhint %} ## Exploit Research Use automated suggestions as a starting point, then confirm the exact kernel, distribution patch level, architecture, and exploit requirements manually. ```bash searchsploit linux kernel searchsploit linux kernel ubuntu searchsploit linux kernel overlayfs ``` Common local kernel escalation families to validate carefully: | Exploit Family | Example CVE | Notes | | --------------- | -------------------------------- | --------------------------------------------------------------------- | | Dirty COW | `CVE-2016-5195` | Older kernel copy-on-write bug; often unstable and version dependent. | | OverlayFS | `CVE-2021-3493`, `CVE-2023-0386` | Ubuntu/kernel-specific OverlayFS privilege escalation paths. | | PTRACE\_TRACEME | `CVE-2019-13272` | Local privilege escalation affecting some Ubuntu apport/pkexec flows. | | Dirty Pipe | `CVE-2022-0847` | Kernel pipe handling bug that can modify protected files at runtime. | ### Dirty COW Check ```bash grep -q "Ubuntu 16.04" /etc/issue && echo "System might be vulnerable to Dirty COW" ``` Compile and run only after confirming applicability in a lab or authorized target: ```bash gcc -pthread dirty.c -o dirty -lcrypt ./dirty password123 ```

:microchip:

Linux Exploit Suggester

Tool (Linux Exploit Suggester) - Privilege Escalation notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Linux Exploit Suggester - Privilege Escalation

:microchip:

Dirty COW Kernel Exploit

Kernel Exploitation (Dirty COW) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Kernel Exploitation (Dirty COW) - Linux Privilege Escalation

:microchip:

Ubuntu 23.04 Kernel Exploit

Kernel Exploitation (Ubuntu 23.04) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Kernel Exploitation (Ubuntu 23.04) - Linux Privilege Escalation

:microchip:

OverlayFS Kernel Exploit

Kernel Exploitation (OverlayFS) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Kernel Exploitation (OverlayFS) - Linux Privilege Escalation

:microchip:

Copy Fail (CVE-2026-31431)

Validate Copy Fail kernel privilege escalation exposure and confirm whether the target system is vulnerable.https://github.com/theori-io/copy-fail-CVE-2026-31431

:microchip:

Ubuntu 16.04 Kernel 4.4.0-116

Linux kernel exploit notes for local privilege escalation, version validation, and safe proof-of-concept testing.Ubuntu 16.04 Kernel 4.4.0-116
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/privesc/kernel-exploitation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.