CVE-2022-0847: Dirty Pipe
- Vendors
- Red HatFedora ProjectNetAppLinuxOvirtSiemensSonicwall
Dirty Pipe is a local privilege-escalation vulnerability in the Linux kernel pipe-buffer implementation. The copy_page_to_iter_pipe() and push_pipe() functions fail to initialize the flags member of newly created pipe_buffer structures, allowing stale PIPE_BUF_FLAG_CAN_MERGE values to persist. An unprivileged local attacker can abuse splice-based pipe operations to overwrite page-cache data backing otherwise read-only files, bypassing file write permissions and potentially obtaining root privileges. The vulnerability affects upstream kernels beginning with Linux 5.8 and was fixed in the 5.10.102, 5.15.25, and 5.16.11 releases; vendor kernels can have different affected and fixed version numbers because of backports.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises file-data integrity by permitting unauthorized modification of read-only file-backed page-cache pages. Modifying security-sensitive account data or setuid-root executables can elevate an unprivileged process to root, enabling complete system compromise, access to sensitive information, and installation of privileged backdoors.
Mitigation
If you can’t patch tonight, do this now.
Until patching is complete, restrict untrusted local access and execution of untrusted applications to reduce exploitation opportunities. Monitor Auditd events for suspicious splice system-call patterns associated with Dirty Pipe exploitation; this provides detection rather than prevention. No vulnerability-specific preventive workaround is established here, and network access controls alone do not prevent exploitation by an attacker already executing locally.
Remediation
Patch, then assume compromise.
Install the latest vendor-supported kernel update addressing CVE-2022-0847 and reboot into the fixed kernel. Upstream fixes are available in Linux 5.10.102, 5.15.25, and 5.16.11 and subsequent releases of those branches. For distribution kernels, use the vendor's fixed package versions rather than relying solely on the upstream version number, because affected code and fixes may be backported.
Exploits
45 exploits validated by Mallory's analysis. Hidden: 13 rejected by Mallory's analysis as not a working exploit; 4 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-0847 exploited in the wild?
- Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 25, 2022.
- Is there a public exploit for CVE-2022-0847?
- Yes. Mallory tracks 45 public exploits or proofs of concept for CVE-2022-0847, the earliest disclosed Feb 20, 2022.
- Is there a patch for CVE-2022-0847?
- Install the latest vendor-supported kernel update addressing CVE-2022-0847 and reboot into the fixed kernel. Upstream fixes are available in Linux 5.10.102, 5.15.25, and 5.16.11 and subsequent releases of those branches.
- What products are affected by CVE-2022-0847?
- Linux Kernel, Red Hat Enterprise Linux Eus, Red Hat Enterprise Linux For Ibm Z Systems, Red Hat Enterprise Linux For Ibm Z Systems Eus, Red Hat Enterprise Linux For Power Little Endian, and at least 24 more.
- How severe is CVE-2022-0847?
- CVE-2022-0847 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 92.8% (100th percentile) as of Oct 25, 2026.
Recent activity
71 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.