> 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/zh/privesc/kernel-exploitation/dirty-cow-kernel-exploit-linux-privilege-escalation.md).
# 内核利用（Dirty COW）- Linux 权限提升
内核利用（Dirty COW）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。
## 这是什么
内核提权针对 Linux 内核中的本地漏洞或发行版特定补丁。这些利用可能不稳定，因此在执行前进行版本验证和实验室测试很重要。此页面具体关注 **内核利用（Dirty COW）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。
## 枚举
在运行利用路径之前，先确认本地环境和具体的配置错误。
```bash
uname -a
cat /etc/os-release
lsb_release -a 2>/dev/null
```
## 示例
## Dirty COW 内核示例
使用 **lsb\_release -a** 以识别操作系统版本。
如果你使用 **search exploit** 命令，你会看到许多与此版本 Ubuntu 相关的内核漏洞。
在这种情况下，我们感兴趣的是：
运行 **脚本** 并为 dirty 用户输入一个密码：
我们成功地 **更改了密码** 在 /etc/passwd 中的 firefart 用户：
我们属于 **root** 组：
---
# 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/zh/privesc/kernel-exploitation/dirty-cow-kernel-exploit-linux-privilege-escalation.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.
