CVE-2026-99664 (GCVE-0-2026-99664)

Vulnerability from cvelistv5 – Published: 2026-11-20 05:50 – Updated: 2026-11-20 05:50
VLAI
Title
mm/gup: recheck the PUD under PTL in follow_pud_mask()
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/gup: recheck the PUD under PTL in follow_pud_mask() follow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes the lock and calls follow_huge_pud(), which reads the entry again, but only tests whether it is present. A leaf can be zapped concurrently and a page fault can fill the empty entry with a page table. This currently only applies when device-dax makes use of PUD entries, and the fault after e.g., MADV_DONTNEED would find THPs to be disabled. That requires a sequence like 1) Fault in the PUD 2) Disable THP 3) Have GUP race against concurrent MADV_DONTNEED + refault Which is rather unlikely to happen in practice, which is why we never received a report about such a problem. Before commit 1b1676180246 ("mm/gup: handle huge pud for follow_pud_mask()"), we performed that check in follow_devmap_pud() by testing for pud_devmap(). Let's fix it by just structuring follow_pud_mask() similar to follow_pmd_mask(), minus protnone stuff that does not apply and minus FOLL_SPLIT_PMD handling. That makes it much easier to spot any such inconsistencies. Perform the pud_bad() check early in follow_pmd_mask() and just forward the PUD value. We can drop the pud_present() check in follow_huge_pud(), just like we have in follow_huge_pmd(). Even though we are performing more changes than strictly necessary, the fix should be easy to backport.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 7143 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 1b1676180246232308885c4f37fee01cf898fdb2 , < da57b6bce646946c083a48df644d43bb9d011f5f (git)
Affected: 1b1676180246232308885c4f37fee01cf898fdb2 , < 9eaedd598cd25eb0e18958e2456153a4c1f3db03 (git)
Affected: 1b1676180246232308885c4f37fee01cf898fdb2 , < 79cb51d538abc459f74e046d27797d36b133ce0e (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.10
Unaffected: 0 , < 6.10 (semver)
Unaffected: 6.18.64 , ≤ 6.18.* (semver)
Unaffected: 7.3.5 , ≤ 7.3.* (semver)
Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/gup.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "da57b6bce646946c083a48df644d43bb9d011f5f",
              "status": "affected",
              "version": "1b1676180246232308885c4f37fee01cf898fdb2",
              "versionType": "git"
            },
            {
              "lessThan": "9eaedd598cd25eb0e18958e2456153a4c1f3db03",
              "status": "affected",
              "version": "1b1676180246232308885c4f37fee01cf898fdb2",
              "versionType": "git"
            },
            {
              "lessThan": "79cb51d538abc459f74e046d27797d36b133ce0e",
              "status": "affected",
              "version": "1b1676180246232308885c4f37fee01cf898fdb2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/gup.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.64",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3.5",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.4-rc2",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/gup: recheck the PUD under PTL in follow_pud_mask()\n\nfollow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes\nthe lock and calls follow_huge_pud(), which reads the entry again, but\nonly tests whether it is present.\n\nA leaf can be zapped concurrently and a page fault can fill the empty\nentry with a page table.\n\nThis currently only applies when device-dax makes use of PUD entries,\nand the fault after e.g., MADV_DONTNEED would find THPs to be disabled.\n\nThat requires a sequence like\n\n1) Fault in the PUD\n2) Disable THP\n3) Have GUP race against concurrent MADV_DONTNEED + refault\n\nWhich is rather unlikely to happen in practice, which is why we never\nreceived a report about such a problem.\n\nBefore commit 1b1676180246 (\"mm/gup: handle huge pud for\nfollow_pud_mask()\"), we performed that check in follow_devmap_pud() by\ntesting for pud_devmap().\n\nLet\u0027s fix it by just structuring follow_pud_mask() similar to\nfollow_pmd_mask(), minus protnone stuff that does not apply and minus\nFOLL_SPLIT_PMD handling. That makes it much easier to spot any such\ninconsistencies.\n\nPerform the pud_bad() check early in follow_pmd_mask() and just forward\nthe PUD value. We can drop the pud_present() check in follow_huge_pud(),\njust like we have in follow_huge_pmd().\n\nEven though we are performing more changes than strictly necessary, the\nfix should be easy to backport."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T05:50:14.863Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/da57b6bce646946c083a48df644d43bb9d011f5f"
        },
        {
          "url": "https://git.kernel.org/stable/c/9eaedd598cd25eb0e18958e2456153a4c1f3db03"
        },
        {
          "url": "https://git.kernel.org/stable/c/79cb51d538abc459f74e046d27797d36b133ce0e"
        }
      ],
      "title": "mm/gup: recheck the PUD under PTL in follow_pud_mask()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99664",
    "datePublished": "2026-11-20T05:50:14.863Z",
    "dateReserved": "2026-09-25T10:25:14.427Z",
    "dateUpdated": "2026-11-20T05:50:14.863Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-99664",
      "date": "2026-11-20",
      "epss": "0.00166",
      "percentile": "0.06029"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "mm/gup.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "da57b6bce646946c083a48df644d43bb9d011f5f",
                    "status": "affected",
                    "version": "1b1676180246232308885c4f37fee01cf898fdb2",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "9eaedd598cd25eb0e18958e2456153a4c1f3db03",
                    "status": "affected",
                    "version": "1b1676180246232308885c4f37fee01cf898fdb2",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "79cb51d538abc459f74e046d27797d36b133ce0e",
                    "status": "affected",
                    "version": "1b1676180246232308885c4f37fee01cf898fdb2",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "mm/gup.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.10"
                  },
                  {
                    "lessThan": "6.10",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.18.*",
                    "status": "unaffected",
                    "version": "6.18.64",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.3.*",
                    "status": "unaffected",
                    "version": "7.3.5",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.4-rc2",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/gup: recheck the PUD under PTL in follow_pud_mask()\n\nfollow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes\nthe lock and calls follow_huge_pud(), which reads the entry again, but\nonly tests whether it is present.\n\nA leaf can be zapped concurrently and a page fault can fill the empty\nentry with a page table.\n\nThis currently only applies when device-dax makes use of PUD entries,\nand the fault after e.g., MADV_DONTNEED would find THPs to be disabled.\n\nThat requires a sequence like\n\n1) Fault in the PUD\n2) Disable THP\n3) Have GUP race against concurrent MADV_DONTNEED + refault\n\nWhich is rather unlikely to happen in practice, which is why we never\nreceived a report about such a problem.\n\nBefore commit 1b1676180246 (\"mm/gup: handle huge pud for\nfollow_pud_mask()\"), we performed that check in follow_devmap_pud() by\ntesting for pud_devmap().\n\nLet\u0027s fix it by just structuring follow_pud_mask() similar to\nfollow_pmd_mask(), minus protnone stuff that does not apply and minus\nFOLL_SPLIT_PMD handling. That makes it much easier to spot any such\ninconsistencies.\n\nPerform the pud_bad() check early in follow_pmd_mask() and just forward\nthe PUD value. We can drop the pud_present() check in follow_huge_pud(),\njust like we have in follow_huge_pmd().\n\nEven though we are performing more changes than strictly necessary, the\nfix should be easy to backport."
          }
        ],
        "id": "CVE-2026-99664",
        "lastModified": "2026-11-20T06:18:00.630",
        "metrics": {},
        "published": "2026-11-20T06:18:00.630",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/79cb51d538abc459f74e046d27797d36b133ce0e"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/9eaedd598cd25eb0e18958e2456153a4c1f3db03"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/da57b6bce646946c083a48df644d43bb9d011f5f"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-20T11:26:10+00:00",
      "cve": "CVE-2026-99664",
      "id": "CVE-2026-99664",
      "initial_release_date": "2026-11-20T05:50:14.863000+00:00",
      "product_status:known_affected": "2",
      "product_status:known_not_affected": "202",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: kernel: Denial of service via race condition in page table handling",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99664.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.