Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect handling of a copy-on-write (COW) feature to write to a read-only memory mapping, as exploited in the wild in October 2016, aka "Dirty COW."
CVE-2016-5195
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.0 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.0
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.7%
- KEV
- ⚠ Exploited
Published
November 10, 2016
Last Modified
April 21, 2026
Advisory Details (4)
Auto-updated May 20, 2026mm: remove gup_flags FOLL_WRITE games from __get_user_pages() - kernel/git/torvalds/linux.git - Linux kernel source tree
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619Patch Availability(24)
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(24)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Red HatRHSA-2016:2098IMPORTANT2016-10-19
RHSA-2016:2098 — Important
- Red HatRHSA-2016:2105IMPORTANT2016-10-19
RHSA-2016:2105 — Important
- Red HatRHSA-2016:2106IMPORTANT2016-10-19
RHSA-2016:2106 — Important
- Red HatRHSA-2016:2107IMPORTANT2016-10-19
RHSA-2016:2107 — Important
- Red HatRHSA-2016:2110IMPORTANT2016-10-19
RHSA-2016:2110 — Important
- Red HatRHSA-2016:2118IMPORTANT2016-10-19
RHSA-2016:2118 — Important
- Red HatRHSA-2016:2120IMPORTANT2016-10-19
RHSA-2016:2120 — Important
- Red HatRHSA-2016:2124IMPORTANT2016-10-19
RHSA-2016:2124 — Important
- Red HatRHSA-2016:2126IMPORTANT2016-10-19
RHSA-2016:2126 — Important
- Red HatRHSA-2016:2127IMPORTANT2016-10-19
RHSA-2016:2127 — Important
- Red HatRHSA-2016:2128IMPORTANT2016-10-19
RHSA-2016:2128 — Important
- Red HatRHSA-2016:2132IMPORTANT2016-10-19
RHSA-2016:2132 — Important
- Red HatRHSA-2016:2133IMPORTANT2016-10-19
RHSA-2016:2133 — Important
- Red HatRHSA-2017:0372IMPORTANT2016-10-19
RHSA-2017:0372 — Important
- UbuntuUSN-3104-1HIGH
Linux kernel vulnerability
- UbuntuUSN-3104-2HIGH
Linux kernel (OMAP4) vulnerability
- UbuntuUSN-3105-1HIGH
Linux kernel vulnerability
- UbuntuUSN-3105-2HIGH
Linux kernel (Trusty HWE) vulnerability
- UbuntuUSN-3106-1HIGH
Linux kernel vulnerability
- UbuntuUSN-3106-2HIGH
Linux kernel (Xenial HWE) vulnerability
- UbuntuUSN-3106-3HIGH
Linux kernel (Raspberry Pi 2) vulnerability
- UbuntuUSN-3106-4HIGH
Linux kernel (Qualcomm Snapdragon) vulnerability
- UbuntuUSN-3107-1HIGH
Linux kernel vulnerability
- UbuntuUSN-3107-2HIGH
Linux kernel (Raspberry Pi 2) vulnerability
Data Freshness Timeline
(refreshed 88× in last 7d / 391× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 733 total refreshes for this CVE.
- 2026-07-23 01:23 UTCEG score recompute
- 2026-07-22 22:02 UTCEG score recompute
- 2026-07-22 20:51 UTCVendor advisory
- 2026-07-22 20:51 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:58 UTCEG score recompute
- 2026-07-22 16:58 UTCVendor advisory
- 2026-07-22 16:58 UTCGHSA enrichment
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 13:04 UTCVendor advisory
- 2026-07-22 13:04 UTCGHSA enrichment
- 2026-07-22 09:11 UTCVendor advisory
- 2026-07-22 09:11 UTCGHSA enrichment
- 2026-07-22 05:18 UTCVendor advisory
- 2026-07-22 05:18 UTCGHSA enrichment
- 2026-07-22 01:02 UTCVendor advisory
- 2026-07-22 01:02 UTCGHSA enrichment
- 2026-07-21 18:06 UTCVendor advisory
- 2026-07-21 18:06 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:11 UTCVendor advisory
- 2026-07-21 14:11 UTCGHSA enrichment
- 2026-07-21 10:18 UTCVendor advisory
- 2026-07-21 10:18 UTCGHSA enrichment
- 2026-07-21 06:24 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 06:24 UTCGHSA enrichment
- 2026-07-21 02:31 UTCVendor advisory
- 2026-07-21 02:31 UTCGHSA enrichment
- 2026-07-20 22:38 UTCVendor advisory
- 2026-07-20 22:38 UTCGHSA enrichment
- 2026-07-20 18:46 UTCEG score recompute
- 2026-07-20 18:46 UTCVendor advisory
- 2026-07-20 18:45 UTCGHSA enrichment
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-20 14:52 UTCVendor advisory
- 2026-07-20 14:52 UTCGHSA enrichment
- 2026-07-20 10:59 UTCVendor advisory
- 2026-07-20 10:58 UTCGHSA enrichment
- 2026-07-20 07:05 UTCVendor advisory
- 2026-07-20 07:05 UTCGHSA enrichment
- 2026-07-20 03:12 UTCVendor advisory
- 2026-07-20 03:11 UTCGHSA enrichment
- 2026-07-19 23:18 UTCVendor advisory
- 2026-07-19 23:18 UTCGHSA enrichment
- 2026-07-19 19:25 UTCVendor advisory
- 2026-07-19 19:25 UTCGHSA enrichment
- 2026-07-19 15:32 UTCVendor advisory
- 2026-07-19 15:32 UTCGHSA enrichment
- 2026-07-19 11:39 UTCVendor advisory
- 2026-07-19 11:39 UTCGHSA enrichment
- 2026-07-19 07:46 UTCVendor advisory
- 2026-07-19 07:46 UTCGHSA enrichment
- 2026-07-19 03:52 UTCVendor advisory
- 2026-07-19 03:52 UTCGHSA enrichment
- 2026-07-18 23:58 UTCVendor advisory
- 2026-07-18 23:58 UTCGHSA enrichment
- 2026-07-18 20:03 UTCVendor advisory
- 2026-07-18 20:02 UTCGHSA enrichment
- 2026-07-18 16:08 UTCVendor advisory
- 2026-07-18 16:07 UTCGHSA enrichment
- 2026-07-18 12:14 UTCVendor advisory
- 2026-07-18 12:14 UTCGHSA enrichment
- 2026-07-18 08:21 UTCVendor advisory
- 2026-07-18 08:21 UTCGHSA enrichment
- 2026-07-18 04:28 UTCVendor advisory
- 2026-07-18 04:28 UTCGHSA enrichment
- 2026-07-18 00:35 UTCVendor advisory
- 2026-07-18 00:35 UTCGHSA enrichment
- 2026-07-17 20:42 UTCVendor advisory
- 2026-07-17 20:42 UTCGHSA enrichment
- 2026-07-17 16:49 UTCVendor advisory
- 2026-07-17 16:48 UTCGHSA enrichment
- 2026-07-17 12:54 UTCVendor advisory
- 2026-07-17 12:54 UTCGHSA enrichment
- 2026-07-17 09:01 UTCEG score recompute
- 2026-07-17 09:01 UTCVendor advisory
- 2026-07-17 09:00 UTCGHSA enrichment
- 2026-07-17 05:06 UTCVendor advisory
- 2026-07-17 05:06 UTCGHSA enrichment
- 2026-07-17 01:14 UTCVendor advisory
- 2026-07-17 01:13 UTCGHSA enrichment
- 2026-07-16 21:20 UTCVendor advisory
- 2026-07-16 21:20 UTCGHSA enrichment
- 2026-07-16 17:27 UTCVendor advisory
- 2026-07-16 17:27 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 13:34 UTCVendor advisory
- 2026-07-16 13:34 UTCGHSA enrichment
- 2026-07-16 09:41 UTCVendor advisory
- 2026-07-16 09:41 UTCGHSA enrichment
- 2026-07-16 05:48 UTCVendor advisory
- 2026-07-16 05:48 UTCGHSA enrichment
- 2026-07-16 01:55 UTCVendor advisory
- 2026-07-16 01:55 UTCGHSA enrichment
- 2026-07-15 22:02 UTCVendor advisory
- 2026-07-15 22:01 UTCGHSA enrichment
- 2026-07-15 18:07 UTCVendor advisory
- 2026-07-15 18:06 UTCGHSA enrichment
Publicly available exploits
(10 references)Working exploit code is in the public domain (7 GitHub PoCs) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCr1is/CVE-2022-0847First seen Mar 7, 2022
CVE-2022-0847-DirtyPipe-Exploit CVE-2022-0847 是存在于 Linux内核 5.8 及之后版本中的本地提权漏洞。攻击者通过利用此漏洞,可覆盖重写任意可读文件中的数据,从而可将普通权限的用户提升到特权 root。 CVE-2022-0847 的漏洞原理类似于 CVE-2016-5195 脏牛漏洞(Dirty Cow),但它更容易被利用。漏洞作者将此漏洞命名为“Dirty Pipe”
Open source ↗ - GitHub PoCBrucetg/DirtyCow-EXPFirst seen May 27, 2018
编译好的脏牛漏洞(CVE-2016-5195)EXP
Open source ↗ - GitHub PoChyln9/VIKIROOTFirst seen Jan 20, 2017
CVE-2016-5195 (Dirty COW) PoC for Android 6.0.1 Marshmallow
Open source ↗ - Exploit-DBEDB-40839✓ verifiedFirst seen Nov 28, 2016
Linux Kernel 2.6.22 < 3.9 - 'Dirty COW' 'PTRACE_POKEDATA' Race Condition Privilege Escalation (/etc/passwd Method)
Open source ↗ - Exploit-DBEDB-40847✓ verifiedFirst seen Nov 27, 2016
Linux Kernel 2.6.22 < 3.9 - 'Dirty COW /proc/self/mem' Race Condition Privilege Escalation (/etc/passwd Method)
Open source ↗ - GitHub PoCfirefart/dirtycowFirst seen Nov 25, 2016
Dirty Cow exploit - CVE-2016-5195
Open source ↗ - GitHub PoCaishee/scan-dirtycowFirst seen Oct 29, 2016
Scan vuls kernel CVE-2016-5195 - DirtyCow
Open source ↗ - Exploit-DBEDB-40838First seen Oct 26, 2016
Linux Kernel 2.6.22 < 3.9 - 'Dirty COW PTRACE_POKEDATA' Race Condition (Write Access Method)
Open source ↗ - GitHub PoCDavidBuchanan314/cowrootFirst seen Oct 24, 2016
Universal Android root tool based on CVE-2016-5195. Watch this space.
Open source ↗ - GitHub PoCgbonacini/CVE-2016-5195First seen Oct 23, 2016
A CVE-2016-5195 exploit example.
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-362
Frequently asked(6)
What is CVE-2016-5195?
When was CVE-2016-5195 disclosed?
Is CVE-2016-5195 actively exploited?
What is the CVSS score of CVE-2016-5195?
Which products are affected by CVE-2016-5195?
How do I remediate CVE-2016-5195?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-5195
Is Your Infrastructure Affected by CVE-2016-5195?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.