CVE-2016-5195

CRITICALNVD 7.09.0
EchelonGraph scoreHIGH confidence

“▲” 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-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.0 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 GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this weekExploited in the wild

Also known asEUVD-2016-6146 (ENISA EUVD) · GHSA-j68w-7qm9-fjqq (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 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
CISA-KEV: ExploitedEPSS PROB: 84%CVSS: 7.0Exploit: Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

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."

CVSS v3
7.0
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG 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
84%
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.GitHub Security Advisory CVSS
EG Likelihood
84% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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-2016-5195

Published

November 10, 2016

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Oct 26, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

mm: 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=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619

Vendor Advisories for CVE-2016-5195(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-extra-4.4.0-45-generic (4.4.0-45.66) @ xenial2026-11-02ubuntu
ubuntulinux-image-3.13.0-100-generic (3.13.0-100.147~precise1) @ precise2026-11-02ubuntu
ubuntulinux-image-4.8.0-1017-raspi2 (4.8.0-1017.20) @ yakkety2026-11-02ubuntu
ubuntulinux-image-4.4.0-1032-snapdragon (4.4.0-1032.36) @ xenial2026-11-02ubuntu
ubuntulinux-image-extra-3.13.0-100-generic (3.13.0-100.147) @ trusty2026-11-02ubuntu
ubuntulinux-image-4.8.0-26-powerpc-e500mc (4.8.0-26.28) @ yakkety2026-11-02ubuntu
ubuntulinux-image-4.4.0-1029-raspi2 (4.4.0-1029.36) @ xenial2026-11-02ubuntu
ubuntulinux-image-extra-4.4.0-45-generic (4.4.0-45.66~14.04.1) @ trusty2026-11-02ubuntu
ubuntulinux-image-3.2.0-1491-omap4 (3.2.0-1491.118) @ precise2026-11-02ubuntu
ubuntulinux-image-3.2.0-113-highbank (3.2.0-113.155) @ precise2026-11-02ubuntu
redhatkernel-aarch64-0:4.5.0-15.2.1.el72017-03-02redhat
redhatkernel-0:2.6.32-220.68.1.el62016-11-01redhat
redhatkernel-0:2.6.32-358.75.1.el62016-11-01redhat
redhatkernel-0:2.6.32-504.54.1.el62016-10-31redhat
redhatkernel-0:2.6.18-238.57.1.el52016-10-31redhat
redhatkernel-0:2.6.18-348.32.1.el52016-10-31redhat
redhatkernel-0:2.6.18-416.el52016-10-28redhat
redhatkernel-0:2.6.32-431.75.1.el62016-10-27redhat
redhatkernel-rt-1:3.10.0-327.rt56.198.el6rt2016-10-26redhat
redhatkernel-0:2.6.32-573.35.2.el62016-10-26redhat
redhatkernel-rt-0:3.10.0-327.36.3.rt56.238.el72016-10-26redhat
redhatkernel-0:3.10.0-229.42.2.ael7b2016-10-26redhat
redhatkernel-0:2.6.32-642.6.2.el62016-10-26redhat
redhatkernel-0:3.10.0-327.36.3.el72016-10-24redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.7.8-1: fixed in 4.7.8-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.7.8-1: fixed in 4.7.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.7.8-1: fixed in 4.7.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.7.8-1: fixed in 4.7.8-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
linux3.2.41-2 ... 3.2.81-2 (60 versions)
  • every version up to 3.2.82-1: fixed in 3.2.82-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (37 versions)
  • every version up to 3.16.36-1+deb8u2: fixed in 3.16.36-1+deb8u2
—

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.

Data Freshness Timeline

(refreshed 27× in last 7d / 198× 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 100 of 1,864 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. None are among the latest 100 rows. The 1,764 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:25 UTCOSV refresh
  2. 2026-11-02 04:48 UTCEG score recompute
  3. 2026-11-02 04:48 UTCVendor advisory
  4. 2026-11-02 04:47 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-01 07:01 UTCEG score recompute
  6. 2026-11-01 07:01 UTCVendor advisory
  7. 2026-11-01 07:01 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-31 16:27 UTCEPSS rescoreEPSS 84% · 99th percentile
  9. 2026-10-31 09:15 UTCEG score recompute
  10. 2026-10-31 09:15 UTCVendor advisory
  11. 2026-10-31 09:15 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-30 11:29 UTCEG score recompute
  13. 2026-10-30 11:29 UTCVendor advisory
  14. 2026-10-30 11:29 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-29 16:27 UTCEPSS rescoreEPSS 84% · 99th percentile
  16. 2026-10-29 13:43 UTCEG score recompute
  17. 2026-10-29 13:43 UTCVendor advisory
  18. 2026-10-29 13:43 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-28 15:55 UTCVendor advisory
  20. 2026-10-28 15:55 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-27 18:10 UTCEG score recompute
  22. 2026-10-27 18:10 UTCVendor advisory
  23. 2026-10-27 18:10 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-27 16:26 UTCEPSS rescoreEPSS 84% · 99th percentile
  25. 2026-10-26 20:24 UTCEG score recompute
Show 75 more
  1. 2026-10-26 20:24 UTCVendor advisory
  2. 2026-10-26 20:24 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-25 22:38 UTCVendor advisory
  4. 2026-10-25 22:38 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-25 19:46 UTCEG score recompute
  6. 2026-10-25 16:27 UTCEPSS rescoreEPSS 84% · 99th percentile
  7. 2026-10-25 00:52 UTCEG score recompute
  8. 2026-10-25 00:52 UTCVendor advisory
  9. 2026-10-25 00:52 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-24 03:07 UTCEG score recompute
  11. 2026-10-24 03:07 UTCVendor advisory
  12. 2026-10-24 03:07 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-23 05:20 UTCEG score recompute
  14. 2026-10-23 05:20 UTCVendor advisory
  15. 2026-10-23 05:20 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-22 16:27 UTCEPSS rescoreEPSS 84% · 99th percentile
  17. 2026-10-22 07:34 UTCEG score recompute
  18. 2026-10-22 07:34 UTCVendor advisory
  19. 2026-10-22 07:34 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-21 16:26 UTCEPSS rescoreEPSS 84% · 99th percentile
  21. 2026-10-21 09:47 UTCEG score recompute
  22. 2026-10-21 09:47 UTCVendor advisory
  23. 2026-10-21 09:47 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-20 16:26 UTCEPSS rescoreEPSS 84% · 99th percentile
  25. 2026-10-20 12:01 UTCEG score recompute
  26. 2026-10-20 12:01 UTCVendor advisory
  27. 2026-10-20 12:01 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-19 14:13 UTCVendor advisory
  29. 2026-10-19 14:13 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  30. 2026-10-18 16:28 UTCEG score recompute
  31. 2026-10-18 16:28 UTCVendor advisory
  32. 2026-10-18 16:27 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-10-18 13:56 UTCVendor advisory
  34. 2026-10-18 13:55 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-18 10:48 UTCEG score recompute
  36. 2026-10-17 16:09 UTCVendor advisory
  37. 2026-10-17 16:09 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-10-16 18:22 UTCEG score recompute
  39. 2026-10-16 18:22 UTCVendor advisory
  40. 2026-10-16 18:22 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-10-16 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  42. 2026-10-15 20:36 UTCEG score recompute
  43. 2026-10-15 20:36 UTCVendor advisory
  44. 2026-10-15 20:35 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-14 22:48 UTCEG score recompute
  46. 2026-10-14 22:48 UTCVendor advisory
  47. 2026-10-14 22:48 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-14 16:27 UTCEPSS rescoreEPSS 84% · 99th percentile
  49. 2026-10-14 00:59 UTCEG score recompute
  50. 2026-10-14 00:59 UTCVendor advisory
  51. 2026-10-14 00:59 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-13 03:12 UTCVendor advisory
  53. 2026-10-13 03:12 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-10-12 20:42 UTCEG score recompute
  55. 2026-10-12 05:24 UTCVendor advisory
  56. 2026-10-12 05:24 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-10-12 01:31 UTCVendor advisory
  58. 2026-10-12 01:31 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-10-11 21:38 UTCEG score recompute
  60. 2026-10-11 21:38 UTCVendor advisory
  61. 2026-10-11 21:38 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-10-11 17:45 UTCEG score recompute
  63. 2026-10-11 17:45 UTCVendor advisory
  64. 2026-10-11 17:45 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-10-11 13:49 UTCEG score recompute
  66. 2026-10-11 13:49 UTCVendor advisory
  67. 2026-10-11 13:49 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-10-11 09:55 UTCVendor advisory
  69. 2026-10-11 09:55 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-10-11 06:02 UTCVendor advisory
  71. 2026-10-11 06:02 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-10-11 02:09 UTCVendor advisory
  73. 2026-10-11 02:08 UTCGHSA enrichmentGHSA-j68w-7qm9-fjqq · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-10 22:12 UTCEG score recompute
  75. 2026-10-10 22:12 UTCVendor advisory

Publicly available exploits

(15 references, 10 shown)

Public exploit code is referenced for this CVE (5 Exploit-DB entries, 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.

  • Exploit-DBEDB-40839✓ verified
    Published 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✓ verified
    Published Nov 27, 2016

    Linux Kernel 2.6.22 < 3.9 - 'Dirty COW /proc/self/mem' Race Condition Privilege Escalation (/etc/passwd Method)

    Open source ↗
  • Exploit-DBEDB-40616✓ verified
    Published Oct 21, 2016

    Linux Kernel 2.6.22 < 3.9 (x86/x64) - 'Dirty COW /proc/self/mem' Race Condition Privilege Escalation (SUID Method)

    Open source ↗
  • Exploit-DBEDB-40611✓ verified
    Published Oct 19, 2016

    Linux Kernel 2.6.22 < 3.9 - 'Dirty COW' /proc/self/mem Race Condition (Write Access Method)

    Open source ↗
  • GitHub PoCr1is/CVE-2022-0847
    Published 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-EXP
    Published May 27, 2018

    编译好的脏牛漏洞(CVE-2016-5195)EXP

    Open source ↗
  • GitHub PoChyln9/VIKIROOT
    Published Jan 20, 2017

    CVE-2016-5195 (Dirty COW) PoC for Android 6.0.1 Marshmallow

    Open source ↗
  • GitHub PoCfirefart/dirtycow
    Published Nov 25, 2016

    Dirty Cow exploit - CVE-2016-5195

    Open source ↗
  • GitHub checkeraishee/scan-dirtycow
    Published Oct 29, 2016

    Scan vuls kernel CVE-2016-5195 - DirtyCow

    Open source ↗
  • Exploit-DBEDB-40838
    Published Oct 26, 2016

    Linux Kernel 2.6.22 < 3.9 - 'Dirty COW PTRACE_POKEDATA' Race Condition (Write Access Method)

    Open source ↗

Frequently asked(6)

What is CVE-2016-5195?
CVE-2016-5195 is a critical-severity vulnerability; its CVE record was published on November 10, 2016. 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."
When was CVE-2016-5195 made public?
CVE-2016-5195 was made public on October 20, 2016: that is the date its CVE record's CNA, Chrome, gives for when the vulnerability was made public. The CVE record itself was published on November 10, 2016. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2016-5195 actively exploited?
Yes. CISA added CVE-2016-5195 to the Known Exploited Vulnerabilities catalog on March 3, 2022, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2016-5195?
CVE-2016-5195 has a CVSS v3 base score of 7.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2016-5195?
CVE-2016-5195 affects Linux Kernel. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2016-5195?
A fix for CVE-2016-5195 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-5195 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-5195

Explore →

Is Your Infrastructure Affected by CVE-2016-5195?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.