Skip to main content
VulnerabilityPublished

CVE-2026-99648: Linux kernel · mm/vma: call ->may_split() before a partial merge

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99648· High

Not known to be exploited · fixed in f437fcb76d448a396940498aba278ac0ad8d715a : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f437fcb76d448a396940498aba278ac0ad8d715a, 456932cdc6eda70b5ad4c628556098846699ab03, 0193e83368022a308d19ee0293f55a4f5d548e40

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to f437fcb76d448a396940498aba278ac0ad8d715a, 456932cdc6eda70b5ad4c628556098846699ab03 or 0193e83368022a308d19ee0293f55a4f5d548e40.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 38607c62b34b46317c46d5baf1df03ac6e48a1c6, < f437fcb76d448a396940498aba278ac0ad8d715a
Fixed in
  • f437fcb76d448a396940498aba278ac0ad8d715a
LinuxLinuxAffected
  • ≥ 38607c62b34b46317c46d5baf1df03ac6e48a1c6, < 456932cdc6eda70b5ad4c628556098846699ab03
Fixed in
  • 456932cdc6eda70b5ad4c628556098846699ab03
LinuxLinuxAffected
  • ≥ 38607c62b34b46317c46d5baf1df03ac6e48a1c6, < 0193e83368022a308d19ee0293f55a4f5d548e40
Fixed in
  • 0193e83368022a308d19ee0293f55a4f5d548e40
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

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 ]

References

Community reviews

Loading reviews…