vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2017-1000405

HIGH
7
CVSS Score
Published: November 30, 2017 at 10:00 PM UTC
Updated: June 17, 2026 at 12:59 AM UTC
1 product affected across 1 vendorLinux Kernel

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7
Exploit prediction
EPSS 3%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel· Linux
95%
3.10.106 ≤ v < 3.113.12.73 ≤ v < 3.133.16.42 ≤ v < 3.16.523.18.55 ≤ v < 3.18.863.2.87 ≤ v < 3.34.1.41 ≤ v < 4.1.484.10 ≤ v < 4.14.44.4.70 ≤ v < 4.4.1044.9.7 ≤ v < 4.9.67
Affected range stops below 3.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.16.52, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.18.86, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.48, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.14.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.4.104, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.67, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (6)

VDB Entryx_refsource_BIDThird Party Advisory
Source: [email protected]
http://www.securityfocus.com/bid/102032
VDB Entryx_refsource_SECTRACKThird Party Advisory
Source: [email protected]
http://www.securitytracker.com/id/1040020
Vendor Advisoryx_refsource_REDHATThird Party Advisory
Source: [email protected]
https://access.redhat.com/errata/RHSA-2018:0180
x_refsource_MISCExploitIssue TrackingThird Party Advisory
Source: [email protected]
https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0
x_refsource_CONFIRMThird Party Advisory
Source: [email protected]
https://source.android.com/security/bulletin/pixel/2018-02-01
Exploitx_refsource_EXPLOIT-DBIssue TrackingThird Party AdvisoryVDB Entry
Source: [email protected]
https://www.exploit-db.com/exploits/43199/

CVSS

7HIGH[email protected]
Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card