CVE-2026-31787
Last modified
CVE-2026-31787 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix double free via VMA splitting privcmd_vm_ops defines .close (privcmd_close), but neither .may_split nor .open. When userspace does a partial munmap() on a privcmd mapping, the kernel splits the VMA via __split_vma(). EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix double free via VMA splitting privcmd_vm_ops defines .close (privcmd_close), but neither .may_split nor .open. When userspace does a partial munmap() on a privcmd mapping, the kernel splits the VMA via __split_vma(). Since may_split is NULL, the split is allowed. vm_area_dup() copies vm_private_data (a pages array allocated in alloc_empty_pages()) into the new VMA without any fixup, because there is no .open callback. Both VMAs now point to the same pages array. When the unmapped portion is closed, privcmd_close() calls: - xen_unmap_domain_gfn_range() - xen_free_unpopulated_pages() - kvfree(pages) The surviving VMA still holds the dangling pointer. When it is later destroyed, the same sequence runs again, which leads to a double free. Fix this issue by adding a .may_split callback denying the VMA split. This is XSA-487 / CVE-2026-31787
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.8, < 5.10.254 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.204 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.170 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.137 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.85 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.26 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.3 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
- http://www.openwall.com/lists/oss-security/2026/04/28/14Mailing List, Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-487.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31787?
How severe is CVE-2026-31787?
How do I fix CVE-2026-31787?
Are you affected by CVE-2026-31787?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
