A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.
CVE-2022-0847
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-04-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under NVD CVSS v3. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 75EG Risk 75/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact. - EPSS PROB
- 93%
- EPSS %ILE
- 99th
- KEV
- ⚠ Exploited
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 93% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.
A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.
In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply updates per vendor instructions.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2022-0847
Published
March 10, 2022
Last Modified
November 6, 2025
Advisory Details (10)
Auto-updated Oct 19, 2026The Dirty Pipe Vulnerability — The Dirty Pipe Vulnerability documentation
https://dirtypipe.cm4all.com/2060795 – (CVE-2022-0847) CVE-2022-0847 kernel: improper initialization of the "flags" member of the new pipe_buffer
Affected: Red Hat Enterprise Linux 8
https://bugzilla.redhat.com/show_bug.cgi?id=2060795Packet Storm
http://packetstormsecurity.com/files/176534/Linux-4.20-KTLS-Read-Only-Write.htmlPacket Storm
http://packetstormsecurity.com/files/166258/Dirty-Pipe-Local-Privilege-Escalation.htmlPacket Storm
http://packetstormsecurity.com/files/166230/Dirty-Pipe-SUID-Binary-Hijack-Privilege-Escalation.htmlVendor Advisories for CVE-2022-0847(9)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2022:0841Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Virtualization Host security and bug fix update [ovirt-4.4.10] Async #1
- CVE-2022-0847Microsoft Security Response Center (MSRC)High
A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.
- RHSA-2022:0831Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security update
- RHSA-2022:0825Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security, bug fix, and enhancement update
- RHSA-2022:0820Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security, bug fix, and enhancement update
- RHSA-2022:0822Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel-rt security update
- RHSA-2022:0823Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security update
- RHSA-2022:0821Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel-rt security and bug fix update
- +1 more
Patch Availability(10)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | linux-image-lowlatency (5.13.0.35.44) @ impish | 2026-10-23 | ubuntu |
| ubuntu | linux-image-unsigned-5.13.0-1010-intel (5.13.0-1010.10) @ focal | 2026-10-23 | ubuntu |
| redhat | redhat-virtualization-host-0:4.4.10-202203101736_8.5 | 2022-03-14 | redhat |
| redhat | kernel-rt-0:4.18.0-305.40.2.rt7.113.el8_4 | 2022-03-10 | redhat |
| redhat | kernel-rt-0:4.18.0-348.20.1.rt7.150.el8_5 | 2022-03-10 | redhat |
| redhat | kernel-0:4.18.0-147.64.1.el8_1 | 2022-03-10 | redhat |
| redhat | kernel-0:4.18.0-348.20.1.el8_5 | 2022-03-10 | redhat |
| redhat | kernel-0:4.18.0-305.40.2.el8_4 | 2022-03-10 | redhat |
| redhat | kernel-0:4.18.0-193.79.1.el8_2 | 2022-03-10 | redhat |
| redhat | kernel-rt-0:4.18.0-193.79.1.rt13.129.el8_2 | 2022-03-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 5.10.46-4 ... 5.10.92-1~bpo10+1 (7 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 17× in last 7d / 161× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 97 of 1,017 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 920 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 12:58 UTCEG score recompute
- 2026-10-23 12:58 UTCVendor advisory
- 2026-10-22 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-10-22 13:39 UTCEG score recompute
- 2026-10-22 13:39 UTCVendor advisory
- 2026-10-21 14:20 UTCEG score recompute
- 2026-10-21 14:20 UTCVendor advisory
- 2026-10-20 16:28 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-10-20 15:03 UTCEG score recompute
- 2026-10-20 15:03 UTCVendor advisory
- 2026-10-19 15:44 UTCEG score recompute
- 2026-10-19 15:44 UTCVendor advisory
- 2026-10-18 16:25 UTCVendor advisory
- 2026-10-18 03:44 UTCEG score recompute
- 2026-10-18 03:44 UTCVendor advisory
- 2026-10-17 04:27 UTCEG score recompute
- 2026-10-17 04:27 UTCVendor advisory
- 2026-10-16 05:09 UTCEG score recompute
- 2026-10-16 05:09 UTCVendor advisory
- 2026-10-15 05:48 UTCEG score recompute
- 2026-10-15 05:48 UTCVendor advisory
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-10-14 06:30 UTCEG score recompute
- 2026-10-14 06:30 UTCVendor advisory
- 2026-10-13 07:11 UTCVendor advisory
Show 72 moreShow fewer
- 2026-10-12 19:04 UTCEG score recompute
- 2026-10-12 07:52 UTCVendor advisory
- 2026-10-12 04:02 UTCVendor advisory
- 2026-10-12 00:13 UTCVendor advisory
- 2026-10-11 20:22 UTCEG score recompute
- 2026-10-11 20:22 UTCVendor advisory
- 2026-10-11 16:34 UTCEG score recompute
- 2026-10-11 16:34 UTCVendor advisory
- 2026-10-11 12:46 UTCEG score recompute
- 2026-10-11 12:46 UTCVendor advisory
- 2026-10-11 08:57 UTCVendor advisory
- 2026-10-11 05:06 UTCVendor advisory
- 2026-10-11 01:18 UTCVendor advisory
- 2026-10-10 21:27 UTCVendor advisory
- 2026-10-10 17:36 UTCVendor advisory
- 2026-10-10 13:48 UTCVendor advisory
- 2026-10-10 10:01 UTCVendor advisory
- 2026-10-10 06:13 UTCVendor advisory
- 2026-10-10 02:24 UTCVendor advisory
- 2026-10-09 22:36 UTCVendor advisory
- 2026-10-09 18:48 UTCVendor advisory
- 2026-10-09 15:01 UTCVendor advisory
- 2026-10-09 11:12 UTCVendor advisory
- 2026-10-09 07:24 UTCVendor advisory
- 2026-10-09 03:36 UTCVendor advisory
- 2026-10-08 23:49 UTCVendor advisory
- 2026-10-08 20:01 UTCVendor advisory
- 2026-10-08 16:12 UTCVendor advisory
- 2026-10-08 12:23 UTCVendor advisory
- 2026-10-08 08:35 UTCVendor advisory
- 2026-10-08 04:47 UTCVendor advisory
- 2026-10-08 01:00 UTCEG score recompute
- 2026-10-08 01:00 UTCVendor advisory
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-10-07 21:12 UTCVendor advisory
- 2026-10-07 17:24 UTCVendor advisory
- 2026-10-07 13:36 UTCVendor advisory
- 2026-10-07 09:49 UTCVendor advisory
- 2026-10-07 06:01 UTCVendor advisory
- 2026-10-07 02:13 UTCVendor advisory
- 2026-10-06 22:25 UTCVendor advisory
- 2026-10-06 18:37 UTCVendor advisory
- 2026-10-06 14:50 UTCVendor advisory
- 2026-10-06 11:02 UTCVendor advisory
- 2026-10-06 07:15 UTCVendor advisory
- 2026-10-06 03:27 UTCVendor advisory
- 2026-10-06 03:26 UTCVendor advisory
- 2026-10-06 03:25 UTCVendor advisory
- 2026-10-05 23:35 UTCVendor advisory
- 2026-10-05 19:47 UTCVendor advisory
- 2026-10-05 16:00 UTCVendor advisory
- 2026-10-05 12:13 UTCVendor advisory
- 2026-10-05 08:25 UTCVendor advisory
- 2026-10-05 04:37 UTCVendor advisory
- 2026-10-05 00:49 UTCVendor advisory
- 2026-10-04 21:00 UTCVendor advisory
- 2026-10-04 17:11 UTCVendor advisory
- 2026-10-04 13:23 UTCVendor advisory
- 2026-10-04 09:36 UTCVendor advisory
- 2026-10-04 05:48 UTCVendor advisory
- 2026-10-04 02:00 UTCVendor advisory
- 2026-10-03 22:13 UTCVendor advisory
- 2026-10-03 18:25 UTCVendor advisory
- 2026-10-03 14:36 UTCVendor advisory
- 2026-10-03 10:48 UTCVendor advisory
- 2026-10-03 07:00 UTCVendor advisory
- 2026-10-03 03:12 UTCVendor advisory
- 2026-10-02 23:25 UTCVendor advisory
- 2026-10-02 19:34 UTCVendor advisory
- 2026-10-02 15:46 UTCVendor advisory
- 2026-10-02 11:59 UTCVendor advisory
- 2026-10-02 08:09 UTCVendor advisory
Publicly available exploits
(12 references, 10 shown)Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 9 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- Metasploitexploit/linux/local/cve_2022_0847_dirtypipe✓ verifiedPublished Mar 10, 2022
Dirty Pipe Local Privilege Escalation via CVE-2022-0847
Open source ↗ - GitHub PoCAlexisAhmed/CVE-2022-0847-DirtyPipe-ExploitsPublished Mar 12, 2022
A collection of exploits and documentation that can be used to exploit the Linux Dirty Pipe vulnerability.
Open source ↗ - GitHub PoCAl1ex/CVE-2022-0847Published Mar 9, 2022
CVE-2022-0847
Open source ↗ - GitHub PoCDataDog/dirtypipe-container-breakout-pocPublished Mar 9, 2022
Container Excape PoC for CVE-2022-0847 "DirtyPipe"
Open source ↗ - Exploit-DBEDB-50808Published Mar 8, 2022
Linux Kernel 5.8 < 5.16.11 - Local Privilege Escalation (DirtyPipe)
Open source ↗ - GitHub checkerbasharkey/CVE-2022-0847-dirty-pipe-checkerPublished Mar 8, 2022
Bash script to check for CVE-2022-0847 "Dirty Pipe"
Open source ↗ - GitHub PoCfebinrev/dirtypipez-exploitPublished Mar 8, 2022
CVE-2022-0847 DirtyPipe Exploit.
Open source ↗ - GitHub PoCknqyf263/CVE-2022-0847Published Mar 8, 2022
The Dirty Pipe Vulnerability
Open source ↗ - GitHub PoCZZ-SOCMAP/CVE-2022-0847Published Mar 8, 2022
Linux Kernel Local Privilege Escalation Vulnerability CVE-2022-0847.
Open source ↗ - GitHub PoCArinerron/CVE-2022-0847-DirtyPipe-ExploitPublished Mar 7, 2022
A root exploit for CVE-2022-0847 (Dirty Pipe)
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2022:0819 · redhat:RHSA-2022:0820 · redhat:RHSA-2022:0825
Frequently asked(6)
What is CVE-2022-0847?
When was the CVE record for CVE-2022-0847 published?
Is CVE-2022-0847 actively exploited?
What is the CVSS score of CVE-2022-0847?
Which products are affected by CVE-2022-0847?
How do I remediate CVE-2022-0847?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-0847
Is Your Infrastructure Affected by CVE-2022-0847?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.