CVE-2017-1000405 public

2017/1000xxx/CVE-2017-1000405.json

@@ -1,19 +1,62 @@
 {
-   "CVE_data_meta" : {
-      "ASSIGNER" : "cve@mitre.org",
-      "DATE_ASSIGNED" : "2017-11-22",
-      "ID" : "CVE-2017-1000405",
-      "STATE" : "RESERVED"
-   },
-   "data_format" : "MITRE",
-   "data_type" : "CVE",
-   "data_version" : "4.0",
-   "description" : {
-      "description_data" : [
-         {
-            "lang" : "eng",
-            "value" : "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided."
-         }
+  "CVE_data_meta": {
+    "ASSIGNER": "kurt@seifried.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": "Linux Kernel",
+                "version": {
+                  "version_data": [
+                    {
+                      "version_value": "2.6.38 through 4.14"
+                    }
+                  ]
+                }
+              }
+            ]
+          },
+          "vendor_name": "Linux Kernel"
+        }
       ]
-   }
+    }
+  },
+  "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": "memory overwrite"
+          }
+        ]
+      }
+    ]
+  },
+  "references": {
+    "reference_data": [
+      {
+        "url": "https://medium.com/bindecy/huge-dirty-cow-cve-2017-1000405-110eca132de0"
+      }
+    ]
+  }
 }