{"api_version":"1","generated_at":"2026-07-23T11:41:01+00:00","cve":"CVE-2017-1000405","urls":{"html":"https://cve.report/CVE-2017-1000405","api":"https://cve.report/api/cve/CVE-2017-1000405.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2017-1000405","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000405"},"summary":{"title":"CVE-2017-1000405","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.","state":"PUBLISHED","assigner":"mitre","published_at":"2017-11-30 22:29:00","updated_at":"2025-04-20 01:37:25"},"problem_types":["CWE-362","n/a"],"metrics":[{"version":"3.1","source":"nvd@nist.gov","type":"Primary","score":"7","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"2.0","source":"nvd@nist.gov","type":"Primary","score":"6.9","severity":"","vector":"AV:L/AC:M/Au:N/C:C/I:C/A:C","data":{"version":"2.0","vectorString":"AV:L/AC:M/Au:N/C:C/I:C/A:C","baseScore":6.9,"accessVector":"LOCAL","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"COMPLETE","integrityImpact":"COMPLETE","availabilityImpact":"COMPLETE"}}],"references":[{"url":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0","name":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Exploit","Issue Tracking","Third Party Advisory"],"title":"“Huge Dirty COW” (CVE-2017–1000405) – Bindecy – Medium","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://www.securityfocus.com/bid/102032","name":"http://www.securityfocus.com/bid/102032","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory","VDB Entry"],"title":"Linux Kernel CVE-2017-1000405 Local Race Condition Vulnerability","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://source.android.com/security/bulletin/pixel/2018-02-01","name":"https://source.android.com/security/bulletin/pixel/2018-02-01","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory"],"title":"Pixel / Nexus Security Bulletin—February 2018  |  Android Open Source Project","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.exploit-db.com/exploits/43199/","name":"https://www.exploit-db.com/exploits/43199/","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Exploit","Issue Tracking","Third Party Advisory","VDB Entry"],"title":"Linux Kernel - 'The Huge Dirty Cow' Overwriting The Huge Zero Page","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://www.securitytracker.com/id/1040020","name":"http://www.securitytracker.com/id/1040020","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory","VDB Entry"],"title":"Linux Kernel Copy-on-Write Memory Management Race Condition May Let Local Users Obtain Elevated Privileges - SecurityTracker","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://access.redhat.com/errata/RHSA-2018:0180","name":"https://access.redhat.com/errata/RHSA-2018:0180","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory"],"title":"Red Hat Customer Portal","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000405","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000405","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"n/a","product":"n/a","version":"affected n/a","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2017","cve_id":"1000405","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"linux","cpe5":"linux_kernel","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2024-08-05T22:00:40.830Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"name":"102032","tags":["vdb-entry","x_refsource_BID","x_transferred"],"url":"http://www.securityfocus.com/bid/102032"},{"name":"RHSA-2018:0180","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred"],"url":"https://access.redhat.com/errata/RHSA-2018:0180"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"},{"tags":["x_refsource_CONFIRM","x_transferred"],"url":"https://source.android.com/security/bulletin/pixel/2018-02-01"},{"name":"1040020","tags":["vdb-entry","x_refsource_SECTRACK","x_transferred"],"url":"http://www.securitytracker.com/id/1040020"},{"name":"43199","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred"],"url":"https://www.exploit-db.com/exploits/43199/"}],"title":"CVE Program Container"}],"cna":{"affected":[{"product":"n/a","vendor":"n/a","versions":[{"status":"affected","version":"n/a"}]}],"dateAssigned":"2017-11-22T00:00:00.000Z","datePublic":"2017-11-27T00:00:00.000Z","descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"description":"n/a","lang":"en","type":"text"}]}],"providerMetadata":{"dateUpdated":"2018-02-12T18:57:01.000Z","orgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca","shortName":"mitre"},"references":[{"name":"102032","tags":["vdb-entry","x_refsource_BID"],"url":"http://www.securityfocus.com/bid/102032"},{"name":"RHSA-2018:0180","tags":["vendor-advisory","x_refsource_REDHAT"],"url":"https://access.redhat.com/errata/RHSA-2018:0180"},{"tags":["x_refsource_MISC"],"url":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"},{"tags":["x_refsource_CONFIRM"],"url":"https://source.android.com/security/bulletin/pixel/2018-02-01"},{"name":"1040020","tags":["vdb-entry","x_refsource_SECTRACK"],"url":"http://www.securitytracker.com/id/1040020"},{"name":"43199","tags":["exploit","x_refsource_EXPLOIT-DB"],"url":"https://www.exploit-db.com/exploits/43199/"}],"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","DATE_ASSIGNED":"2017-11-22","ID":"CVE-2017-1000405","REQUESTER":"contact@bindecy.com","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"102032","refsource":"BID","url":"http://www.securityfocus.com/bid/102032"},{"name":"RHSA-2018:0180","refsource":"REDHAT","url":"https://access.redhat.com/errata/RHSA-2018:0180"},{"name":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0","refsource":"MISC","url":"https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"},{"name":"https://source.android.com/security/bulletin/pixel/2018-02-01","refsource":"CONFIRM","url":"https://source.android.com/security/bulletin/pixel/2018-02-01"},{"name":"1040020","refsource":"SECTRACK","url":"http://www.securitytracker.com/id/1040020"},{"name":"43199","refsource":"EXPLOIT-DB","url":"https://www.exploit-db.com/exploits/43199/"}]}}}},"cveMetadata":{"assignerOrgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca","assignerShortName":"mitre","cveId":"CVE-2017-1000405","datePublished":"2017-11-30T22:00:00.000Z","dateReserved":"2017-11-29T00:00:00.000Z","dateUpdated":"2024-08-05T22:00:40.830Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.1"},"nvd":{"publishedDate":"2017-11-30 22:29:00","lastModifiedDate":"2025-04-20 01:37:25","problem_types":["CWE-362","n/a"],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1,"impactScore":5.9}],"cvssMetricV2":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"2.0","vectorString":"AV:L/AC:M/Au:N/C:C/I:C/A:C","baseScore":6.9,"accessVector":"LOCAL","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"COMPLETE","integrityImpact":"COMPLETE","availabilityImpact":"COMPLETE"},"baseSeverity":"MEDIUM","exploitabilityScore":3.4,"impactScore":10,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.2.87","versionEndExcluding":"3.3","matchCriteriaId":"EDF220AE-D4D3-4C0B-BFCA-4DDB897A81FA"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.10.106","versionEndExcluding":"3.11","matchCriteriaId":"37623D83-3245-418B-AA79-7FFB56124AAB"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.12.73","versionEndExcluding":"3.13","matchCriteriaId":"AB8D1C8F-5DE4-4255-B35E-85BEE71D518A"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.16.42","versionEndExcluding":"3.16.52","matchCriteriaId":"6D8C2C4B-81CA-4D5D-9B18-6D93FC1B1B5B"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.18.55","versionEndExcluding":"3.18.86","matchCriteriaId":"B38F58F2-22F3-41A2-B43D-FD9027FD2A7D"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.1.41","versionEndExcluding":"4.1.48","matchCriteriaId":"871C0EA3-24B8-4D57-A72C-42F66AEED6D0"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.4.70","versionEndExcluding":"4.4.104","matchCriteriaId":"FCBEC938-9743-47A8-B536-D7B935A453A3"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.9.7","versionEndExcluding":"4.9.67","matchCriteriaId":"1D4E9DE9-EA55-48F6-88BB-DBF18E65D76A"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10","versionEndExcluding":"4.14.4","matchCriteriaId":"526A67F6-8D42-4C55-99BE-B68231777244"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2017","CveId":"1000405","Ordinal":"1","Title":"CVE-2017-1000405","CVE":"CVE-2017-1000405","Year":"2017"},"notes":[{"CveYear":"2017","CveId":"1000405","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"CVE-2017-1000405"},{"CveYear":"2017","CveId":"1000405","Ordinal":"2","NoteData":"2017-11-30","Type":"Other","Title":"Published"},{"CveYear":"2017","CveId":"1000405","Ordinal":"3","NoteData":"2018-02-12","Type":"Other","Title":"Modified"}]}}}