FKIE_CVE-2026-99648

Vulnerability from fkie_nvd - Published: 2026-11-20 06:17 - Updated: 2026-11-20 06:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/vma: call ->may_split() before a partial merge A driver can use the ->may_split() hook to forbid a VMA boundary at certain addresses. A device-dax device is a character device that gives raw access to a range of memory through mmap(). device-dax refuses any address that is not a multiple of the device's alignment through vm_ops->may_split. vma_merge_existing_range() can move boundaries, but does not call vm_ops->may_split. If a range at the edge of a VMA gets the attributes of the adjacent VMA, the function moves only that range over to the neighbour: one VMA shrinks and the other grows. This is a partial merge, and vma_modify() tries it before any split. Take a device-dax VMA that lies next to another VMA of the same file. The user calls mprotect() on the one page of the first VMA that touches the second VMA, and asks for the protection that the second VMA already has. The result is a partial merge. It puts the boundary inside a 1 GiB mapping, which is a single leaf entry at the PUD level. As part of the merge, the kernel looks for a huge PMD to split at the new boundary. That code does not expect a PUD leaf: vma_merge_existing_range() commit_merge() vma_adjust_trans_huge() split_huge_pmd_address() mm_find_pmd() treats the PUD leaf as a pointer to a PMD table, so the "table" is the device memory that the leaf maps __split_huge_pmd() reads a PMD that the user wrote to the device memory folio_put() on the folio that this PMD names Bad. While the code must at some point be taught to split PUD entries as well, the issue here is that we move VMA boundaries such that they are incompatible with the driver. Fix this by calling ->may_split() on the address that a partial merge would move the boundary to, and by abandoning the merge if the driver refuses. vma_modify() then tries the split, which fails with -EINVAL. Factor out existing split handling into check_split() and reuse it. Fix generated by an LLM and sent by Chris Mason in private. [ david: improve description; cleanup the code ]
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/vma.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f437fcb76d448a396940498aba278ac0ad8d715a",
              "status": "affected",
              "version": "38607c62b34b46317c46d5baf1df03ac6e48a1c6",
              "versionType": "git"
            },
            {
              "lessThan": "456932cdc6eda70b5ad4c628556098846699ab03",
              "status": "affected",
              "version": "38607c62b34b46317c46d5baf1df03ac6e48a1c6",
              "versionType": "git"
            },
            {
              "lessThan": "0193e83368022a308d19ee0293f55a4f5d548e40",
              "status": "affected",
              "version": "38607c62b34b46317c46d5baf1df03ac6e48a1c6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/vma.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.15"
            },
            {
              "lessThan": "6.15",
              "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/vma: call -\u003emay_split() before a partial merge\n\nA driver can use the -\u003emay_split() hook to forbid a VMA boundary at\ncertain addresses.\n\nA device-dax device is a character device that gives raw access to a\nrange of memory through mmap(). device-dax refuses any address that is not\na multiple of the device\u0027s alignment through vm_ops-\u003emay_split.\n\nvma_merge_existing_range() can move boundaries, but does not call\nvm_ops-\u003emay_split.\n\nIf a range at the edge of a VMA gets the attributes of the adjacent VMA,\nthe function moves only that range over to the neighbour: one VMA shrinks\nand the other grows. This is a partial merge, and vma_modify() tries it\nbefore any split.\n\nTake a device-dax VMA that lies next to another VMA of the same file.\nThe user calls mprotect() on the one page of the first VMA that touches\nthe second VMA, and asks for the protection that the second VMA already\nhas. The result is a partial merge. It puts the boundary inside a 1 GiB\nmapping, which is a single leaf entry at the PUD level.\n\nAs part of the merge, the kernel looks for a huge PMD to split at the\nnew boundary. That code does not expect a PUD leaf:\n\n    vma_merge_existing_range()\n      commit_merge()\n        vma_adjust_trans_huge()\n          split_huge_pmd_address()\n            mm_find_pmd()\n              treats the PUD leaf as a pointer to a PMD table,\n              so the \"table\" is the device memory that the leaf maps\n            __split_huge_pmd()\n              reads a PMD that the user wrote to the device memory\n              folio_put() on the folio that this PMD names\n\nBad. While the code must at some point be taught to split PUD entries as\nwell, the issue here is that we move VMA boundaries such that they are\nincompatible with the driver.\n\nFix this by calling -\u003emay_split() on the address that a partial merge\nwould move the boundary to, and by abandoning the merge if the driver\nrefuses. vma_modify() then tries the split, which fails with -EINVAL.\n\nFactor out existing split handling into check_split() and reuse it.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\n[ david: improve description; cleanup the code ]"
    }
  ],
  "id": "CVE-2026-99648",
  "lastModified": "2026-11-20T06:17:58.427",
  "metrics": {},
  "published": "2026-11-20T06:17:58.427",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/0193e83368022a308d19ee0293f55a4f5d548e40"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/456932cdc6eda70b5ad4c628556098846699ab03"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f437fcb76d448a396940498aba278ac0ad8d715a"
    }
  ],
  "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.