CVE-2026-99648
Severity unknownNo known exploitationFix availablemm/vma: call ->may_split() before a partial merge
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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 ]
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 38607c62b34b46317c46d5baf1df03ac6e48a1c6 before 456932cdc6eda70b5ad4c628556098846699ab03 | 456932cdc6eda70b5ad4c628556098846699ab03 | CVE Program |
| Linux | Linux | from 38607c62b34b46317c46d5baf1df03ac6e48a1c6 before 0193e83368022a308d19ee0293f55a4f5d548e40 | 0193e83368022a308d19ee0293f55a4f5d548e40 | CVE Program |
| Linux | Linux | from 38607c62b34b46317c46d5baf1df03ac6e48a1c6 before f437fcb76d448a396940498aba278ac0ad8d715a | f437fcb76d448a396940498aba278ac0ad8d715a | CVE Program |
| Linux | Linux | 6.15 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.15 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)