CVE-2017-1000405

{"containers": {"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/"}]}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-05T22:00:40.830Z"}, "title": "CVE Program Container", "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/"}]}]}, "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"}

{}

{"affected": [{"affectedData": [{"product": "n/a", "vendor": "n/a", "versions": [{"status": "affected", "version": "n/a"}]}], "source": "cve@mitre.org"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "EDF220AE-D4D3-4C0B-BFCA-4DDB897A81FA", "versionEndExcluding": "3.3", "versionStartIncluding": "3.2.87", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "37623D83-3245-418B-AA79-7FFB56124AAB", "versionEndExcluding": "3.11", "versionStartIncluding": "3.10.106", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "AB8D1C8F-5DE4-4255-B35E-85BEE71D518A", "versionEndExcluding": "3.13", "versionStartIncluding": "3.12.73", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "6D8C2C4B-81CA-4D5D-9B18-6D93FC1B1B5B", "versionEndExcluding": "3.16.52", "versionStartIncluding": "3.16.42", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "B38F58F2-22F3-41A2-B43D-FD9027FD2A7D", "versionEndExcluding": "3.18.86", "versionStartIncluding": "3.18.55", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "871C0EA3-24B8-4D57-A72C-42F66AEED6D0", "versionEndExcluding": "4.1.48", "versionStartIncluding": "4.1.41", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "FCBEC938-9743-47A8-B536-D7B935A453A3", "versionEndExcluding": "4.4.104", "versionStartIncluding": "4.4.70", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "1D4E9DE9-EA55-48F6-88BB-DBF18E65D76A", "versionEndExcluding": "4.9.67", "versionStartIncluding": "4.9.7", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "526A67F6-8D42-4C55-99BE-B68231777244", "versionEndExcluding": "4.14.4", "versionStartIncluding": "4.10", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "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."}, {"lang": "es", "value": "El kernel de Linux desde la versi\u00f3n 2.6.38 hasta la 4.14 presenta un uso problem\u00e1tico de pmd_mkdirty() en la funci\u00f3n touch_pmd() dentro de la implementaci\u00f3n THP. Se puede llegar a touch_pmd() con get_user_pages(). En ese caso, el pmd se ensuciar\u00eda. Este escenario rompe la nueva l\u00f3gica de can_follow_write_pmd(). pmd puede contaminarse sin pasar por un ciclo COW. Este fallo no es tan severo como el error original \"Dirty COW\" porque un archivo ext4 (o cualquier otro archivo normal) no puede ser mapeado usando THP. Sin embargo, permite sobrescribir huge pages de solo lectura. Por ejemplo, los archivos shmem sellados y huge pages con ceros pueden sobrescribirse (ya que se pueden mapear con THP). Tenga en cuenta que despu\u00e9s del primer error de escritura de p\u00e1gina en la p\u00e1gina con cero, se reemplazar\u00e1 por un nuevo thp (y con ceros)."}], "id": "CVE-2017-1000405", "lastModified": "2026-06-17T00:59:06.823", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "MEDIUM", "accessVector": "LOCAL", "authentication": "NONE", "availabilityImpact": "COMPLETE", "baseScore": 6.9, "confidentialityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0"}, "exploitabilityScore": 3.4, "impactScore": 10.0, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "nvd@nist.gov", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "HIGH", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.0, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.0, "impactScore": 5.9, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2017-11-30T22:29:00.217", "references": [{"source": "cve@mitre.org", "tags": ["Third Party Advisory", "VDB Entry"], "url": "http://www.securityfocus.com/bid/102032"}, {"source": "cve@mitre.org", "tags": ["Third Party Advisory", "VDB Entry"], "url": "http://www.securitytracker.com/id/1040020"}, {"source": "cve@mitre.org", "tags": ["Third Party Advisory"], "url": "https://access.redhat.com/errata/RHSA-2018:0180"}, {"source": "cve@mitre.org", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "url": "https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"}, {"source": "cve@mitre.org", "tags": ["Third Party Advisory"], "url": "https://source.android.com/security/bulletin/pixel/2018-02-01"}, {"source": "cve@mitre.org", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory", "VDB Entry"], "url": "https://www.exploit-db.com/exploits/43199/"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory", "VDB Entry"], "url": "http://www.securityfocus.com/bid/102032"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory", "VDB Entry"], "url": "http://www.securitytracker.com/id/1040020"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory"], "url": "https://access.redhat.com/errata/RHSA-2018:0180"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "url": "https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory"], "url": "https://source.android.com/security/bulletin/pixel/2018-02-01"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory", "VDB Entry"], "url": "https://www.exploit-db.com/exploits/43199/"}], "sourceIdentifier": "cve@mitre.org", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-362"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"acknowledgement": "Red Hat would like to thank Daniel Shapiro and Eylon Ben Yaakov for reporting this issue.", "affected_release": [{"advisory": "RHSA-2018:0180", "cpe": "cpe:/o:redhat:enterprise_linux:7", "package": "kernel-alt-0:4.11.0-44.4.1.el7a", "product_name": "Red Hat Enterprise Linux 7", "release_date": "2018-01-25T00:00:00Z"}], "bugzilla": {"description": "kernel: pmd can become dirty without going through a COW cycle", "id": "1516514", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1516514"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.1", "cvss3_scoring_vector": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L", "status": "verified"}, "cwe": "CWE-362", "details": ["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.", "A flaw was found in the patches used to fix the 'dirtycow' vulnerability (CVE-2016-5195). An attacker, able to run local code, can exploit a race condition in transparent huge pages to modify usually read-only huge pages."], "mitigation": {"lang": "en:us", "value": "Disabling the use of zero page:\nIt is possible to prevent the zero page from being mapped as a huge page, by modifying a configuration tunable in the /sys directory as shown below. This prevents the flaw from being exercised in this method.\n# echo 0 > /sys/kernel/mm/transparent_hugepage/use_zero_page\nDisabling huge pages:\nIt is possible to mitigate this flaw by disabling hugepages on a system. Some user applications may require hugepages to be performant, and may suffer a performance penalty when running without hugepages.\nRed Hat has existing solutions created instructing how to disable transparent\nHow to disable transparent hugepages (THP) on Red Hat Enterprise Linux 7\nhttps://access.redhat.com/solutions/1320153\nIf your application may require transparent huge pages, please consult your software vendor to confirm."}, "name": "CVE-2017-1000405", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:5", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 5"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/a:redhat:enterprise_mrg:2", "fix_state": "Not affected", "package_name": "realtime-kernel", "product_name": "Red Hat Enterprise MRG 2"}], "public_date": "2017-11-30T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2017-1000405\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-1000405"], "statement": "From the initial flaw description released, this issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. They do not contain the upstream commit (8310d48b125d19fcd9521d83b8293e63eb1646aa) which allows the race condition.\nThis issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux for Power LE.\nFuture Linux kernel updates for the respective releases may address this issue.\nFor further information please refer to the vulnerability article in the Customer Portal: https://access.redhat.com/security/vulnerabilities/3253921", "threat_severity": "Important"}

{}