CVE-2026-99580 (GCVE-0-2026-99580)

Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49
VLAI
Title
mm/userfaultfd: only allocate anon_vma in CoW mappings
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/userfaultfd: only allocate anon_vma in CoW mappings find_vma_and_prepare_anon() can end up allocating an anon_vma in VMAs that are not CoW mappings, which is wrong. If we have a MAP_SHARED R/O file mapped, we lack VM_SHARED (but do have VM_MAYSHARE) and lack VM_MAYWRITE. While uffd later rejects such mappings (uffd registration requires VM_MAYWRITE, see comment in validate_dst_vma) find_vma_and_prepare_anon() still wrongly allocates an anon vma before it validates the vma. This in turn later confuses copy_page_range()->vma_needs_copy() such that we end up calling copy_hugetlb_page_range() with ranges that actually do not contain *any* per-pagetable information that would require copying, which is the basis for PMD-table sharing in the first place. copy_hugetlb_page_range() should not have to worry about shared PMD tables at all: it doesn't make any sense to copy page tables that are shared, as they can be fully recreated later. Ending up in the function with shareable page tables is the real issue. If a destination PMD table is shared in copy_hugetlb_page_range(), it might get concurrently unshared as we are not holding relevant locks, resulting in us using a page table that is no longer mapped and possibly freed after calling: dst_pte = huge_pte_alloc(dst, dst_vma, addr, sz); To fix it, do not allocate an anon_vma in non-CoW mappings and add a safety guard to copy_hugetlb_page_range(), making sure that we never end up messing with shared PMD tables in there. Before commit 867a43a34ff8a ("userfaultfd: use per-vma locks in userfaultfd operations") we would always validate the VMA before allocating an anon_vma, and consequently never wrongly allocate an anon_vma. As uffd_lock_vma() is part of the same lookup machinery and also contains a misleading VM_SHARED check, change that one as well directly for consistency. A follow-up cleanup will stop taking the hugetlb_vma_lock_read(src_vma) lock in copy_hugetlb_page_range() entirely. Further, the usage of VM_SHARED in userfaultfd code should be cleaned up later to focus on CoW vs. non-CoW mappings.
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: 867a43a34ff8a38772212045262b2c9b77807ea3 , < a90e7044b34f801fbafcb682e8ee827a6db26002 (git)
Affected: 867a43a34ff8a38772212045262b2c9b77807ea3 , < 3bf446c8ce64938f86439906d730a2cd5c0b31e2 (git)
Affected: 867a43a34ff8a38772212045262b2c9b77807ea3 , < 20704188d669ed74a624fd67dfa4711bcb1087b6 (git)
Affected: 867a43a34ff8a38772212045262b2c9b77807ea3 , < 514c9247db305922591d806ec65d3c3fe420538d (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.9
Unaffected: 0 , < 6.9 (semver)
Unaffected: 6.12.118 , ≤ 6.12.* (semver)
Unaffected: 6.18.64 , ≤ 6.18.* (semver)
Unaffected: 7.3.5 , ≤ 7.3.* (semver)
Unaffected: 7.4-rc1 , ≤ * (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/hugetlb.c",
            "mm/userfaultfd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a90e7044b34f801fbafcb682e8ee827a6db26002",
              "status": "affected",
              "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
              "versionType": "git"
            },
            {
              "lessThan": "3bf446c8ce64938f86439906d730a2cd5c0b31e2",
              "status": "affected",
              "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
              "versionType": "git"
            },
            {
              "lessThan": "20704188d669ed74a624fd67dfa4711bcb1087b6",
              "status": "affected",
              "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
              "versionType": "git"
            },
            {
              "lessThan": "514c9247db305922591d806ec65d3c3fe420538d",
              "status": "affected",
              "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/hugetlb.c",
            "mm/userfaultfd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.9"
            },
            {
              "lessThan": "6.9",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.118",
              "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-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.118",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.64",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3.5",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.4-rc1",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/userfaultfd: only allocate anon_vma in CoW mappings\n\nfind_vma_and_prepare_anon() can end up allocating an anon_vma in VMAs that\nare not CoW mappings, which is wrong.\n\nIf we have a MAP_SHARED R/O file mapped, we lack VM_SHARED (but do have\nVM_MAYSHARE) and lack VM_MAYWRITE.\n\nWhile uffd later rejects such mappings (uffd registration requires\nVM_MAYWRITE, see comment in validate_dst_vma) find_vma_and_prepare_anon()\nstill wrongly allocates an anon vma before it validates the vma.\n\nThis in turn later confuses copy_page_range()-\u003evma_needs_copy() such\nthat we end up calling copy_hugetlb_page_range() with ranges that\nactually do not contain *any* per-pagetable information that would\nrequire copying, which is the basis for PMD-table sharing in the first\nplace.\n\ncopy_hugetlb_page_range() should not have to worry about shared\nPMD tables at all: it doesn\u0027t make any sense to copy page tables that are\nshared, as they can be fully recreated later. Ending up in the function\nwith shareable page tables is the real issue.\n\nIf a destination PMD table is shared in copy_hugetlb_page_range(), it\nmight get concurrently unshared as we are not holding relevant\nlocks, resulting in us using a page table that is no longer mapped and\npossibly freed after calling:\n\n\tdst_pte = huge_pte_alloc(dst, dst_vma, addr, sz);\n\nTo fix it, do not allocate an anon_vma in non-CoW mappings and add a\nsafety guard to copy_hugetlb_page_range(), making sure that we never\nend up messing with shared PMD tables in there.\n\nBefore commit 867a43a34ff8a (\"userfaultfd: use per-vma locks in userfaultfd\noperations\") we would always validate the VMA before allocating an\nanon_vma, and consequently never wrongly allocate an anon_vma.\n\nAs uffd_lock_vma() is part of the same lookup machinery and\nalso contains a misleading VM_SHARED check, change that one as well\ndirectly for consistency.\n\nA follow-up cleanup will stop taking the hugetlb_vma_lock_read(src_vma)\nlock in copy_hugetlb_page_range() entirely. Further, the usage of\nVM_SHARED in userfaultfd code should be cleaned up later to focus on\nCoW vs. non-CoW mappings."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T05:49:12.114Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a90e7044b34f801fbafcb682e8ee827a6db26002"
        },
        {
          "url": "https://git.kernel.org/stable/c/3bf446c8ce64938f86439906d730a2cd5c0b31e2"
        },
        {
          "url": "https://git.kernel.org/stable/c/20704188d669ed74a624fd67dfa4711bcb1087b6"
        },
        {
          "url": "https://git.kernel.org/stable/c/514c9247db305922591d806ec65d3c3fe420538d"
        }
      ],
      "title": "mm/userfaultfd: only allocate anon_vma in CoW mappings",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99580",
    "datePublished": "2026-11-20T05:49:12.114Z",
    "dateReserved": "2026-09-25T10:25:14.423Z",
    "dateUpdated": "2026-11-20T05:49:12.114Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "mm/hugetlb.c",
                  "mm/userfaultfd.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "a90e7044b34f801fbafcb682e8ee827a6db26002",
                    "status": "affected",
                    "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "3bf446c8ce64938f86439906d730a2cd5c0b31e2",
                    "status": "affected",
                    "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "20704188d669ed74a624fd67dfa4711bcb1087b6",
                    "status": "affected",
                    "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "514c9247db305922591d806ec65d3c3fe420538d",
                    "status": "affected",
                    "version": "867a43a34ff8a38772212045262b2c9b77807ea3",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "mm/hugetlb.c",
                  "mm/userfaultfd.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.9"
                  },
                  {
                    "lessThan": "6.9",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.12.*",
                    "status": "unaffected",
                    "version": "6.12.118",
                    "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-rc1",
                    "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/userfaultfd: only allocate anon_vma in CoW mappings\n\nfind_vma_and_prepare_anon() can end up allocating an anon_vma in VMAs that\nare not CoW mappings, which is wrong.\n\nIf we have a MAP_SHARED R/O file mapped, we lack VM_SHARED (but do have\nVM_MAYSHARE) and lack VM_MAYWRITE.\n\nWhile uffd later rejects such mappings (uffd registration requires\nVM_MAYWRITE, see comment in validate_dst_vma) find_vma_and_prepare_anon()\nstill wrongly allocates an anon vma before it validates the vma.\n\nThis in turn later confuses copy_page_range()-\u003evma_needs_copy() such\nthat we end up calling copy_hugetlb_page_range() with ranges that\nactually do not contain *any* per-pagetable information that would\nrequire copying, which is the basis for PMD-table sharing in the first\nplace.\n\ncopy_hugetlb_page_range() should not have to worry about shared\nPMD tables at all: it doesn\u0027t make any sense to copy page tables that are\nshared, as they can be fully recreated later. Ending up in the function\nwith shareable page tables is the real issue.\n\nIf a destination PMD table is shared in copy_hugetlb_page_range(), it\nmight get concurrently unshared as we are not holding relevant\nlocks, resulting in us using a page table that is no longer mapped and\npossibly freed after calling:\n\n\tdst_pte = huge_pte_alloc(dst, dst_vma, addr, sz);\n\nTo fix it, do not allocate an anon_vma in non-CoW mappings and add a\nsafety guard to copy_hugetlb_page_range(), making sure that we never\nend up messing with shared PMD tables in there.\n\nBefore commit 867a43a34ff8a (\"userfaultfd: use per-vma locks in userfaultfd\noperations\") we would always validate the VMA before allocating an\nanon_vma, and consequently never wrongly allocate an anon_vma.\n\nAs uffd_lock_vma() is part of the same lookup machinery and\nalso contains a misleading VM_SHARED check, change that one as well\ndirectly for consistency.\n\nA follow-up cleanup will stop taking the hugetlb_vma_lock_read(src_vma)\nlock in copy_hugetlb_page_range() entirely. Further, the usage of\nVM_SHARED in userfaultfd code should be cleaned up later to focus on\nCoW vs. non-CoW mappings."
          }
        ],
        "id": "CVE-2026-99580",
        "lastModified": "2026-11-20T06:17:49.237",
        "metrics": {},
        "published": "2026-11-20T06:17:49.237",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/20704188d669ed74a624fd67dfa4711bcb1087b6"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/3bf446c8ce64938f86439906d730a2cd5c0b31e2"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/514c9247db305922591d806ec65d3c3fe420538d"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/a90e7044b34f801fbafcb682e8ee827a6db26002"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    }
  }
}



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.