CVE-2017-1000405
A public proof of concept exists; no exploitation attested.
- Published2017-11-30
- Fixed in4.14.4 · 4.9.67 · 4.4.104 · 4.1.48 · 3.18.86 · 3.16.52
- WeaknessCWE-362
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The Linux Kernel versions 2.6.38 through 4.14 have a problematic use of pmd_mkdirty() in the touch_pmd() function inside the THP implementation. touch_pmd() can be reached by get_user_pages(). In such case, the pmd will become dirty. This scenario breaks the new can_follow_write_pmd()'s logic - pmd can become dirty without going through a COW cycle. This bug is not as severe as the original "Dirty cow" because an ext4 file (or any other regular file) cannot be mapped using THP. Nevertheless, it does allow us to overwrite read-only huge pages. For example, the zero huge page and sealed shmem files can be overwritten (since their mapping can be populated using THP). Note that after the first write page-fault to the zero page, it will be replaced with a new fresh (and zeroed) thp.
Timeline
dates in UTC- 2017-11-3022:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-1000405?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-1000405?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | ≥ 4.10, < 4.14.4 | 4.14.4 | NVD |
| 4.9 | ≥ 4.9.7, < 4.9.67 | 4.9.67 | NVD |
| 4.4 | ≥ 4.4.70, < 4.4.104 | 4.4.104 | NVD |
| 4.1 | ≥ 4.1.41, < 4.1.48 | 4.1.48 | NVD |
| 3.18 | ≥ 3.18.55, < 3.18.86 | 3.18.86 | NVD |
| 3.16 | ≥ 3.16.42, < 3.16.52 | 3.16.52 | NVD |
| 3.x | ≥ 3.12.73, < 3.13 | 3.13 | NVD |
| 3.x | ≥ 3.10.106, < 3.11 | 3.11 | NVD |
| 3.x | ≥ 3.2.87, < 3.3 | 3.3 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Linux linux kernel to 4.14.4 · 4.9.67 · 4.4.104 · 4.1.48 · 3.18.86 · 3.16.52 · 3.13 · 3.11
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVSS 3.17read 2026-10-23
- NVDCVSS 2.06.9read 2026-10-23
- NVDweakness (CWE)CWE-362read 2026-10-23
- FIRST EPSSEPSS score2.8 %2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-11-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-1000405?
Is CVE-2017-1000405 actively exploited?
What is the CVSS score for CVE-2017-1000405?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.