CVE-2026-31787

High

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

SeverityHigh
CVSS7.8
Exploit probability—
ProductLinux Kernel
PublishedApr 30, 2026
First seenApr 30, 2026
Weakness typeCWE-415CWE-415

How to fix

Affected products

ProductAffected versionsFixed in
linux linux_kernel3.8 ≤ v < 5.10.254, 5.11 ≤ v < 5.15.204, 5.16 ≤ v < 6.1.170, 6.2 ≤ v < 6.6.137, 6.7 ≤ v < 6.12.85, 6.13 ≤ v < 6.18.26, 6.19 ≤ v < 7.0.3, 7.15.10.254, 5.15.204, 6.1.170, 6.6.137, 6.12.85, 6.18.26, 7.0.3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.