KernelScan.io

HIGH Introduced in 6.15

x86-mm CPACollapse UAF

CVE-2026-97943

CVSS 7.0 / 10.0 KernelScan AI

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

01

In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF x86 implements page attribute modification using its Change Page Attributes (CPA) mechanism. This tracks properties of ranges such as cache mode through x86 page attributes, and as part of that logic manipulates kernel page tables. Since commit: 41d88484c71c ("x86/mm/pat: restore large ROX pages after fragmentation") ranges of kernel page table entries can be collapsed into huge page table entries as part of this logic. As part of this collapse, it frees the page tables which the collapsed entries previously pointed to, and it does so without any relevant locks being held to preclude concurrent kernel page table walkers. The only way this code can be reached is if CPA_COLLAPSE is specified, and this is only set in set_memory_rox() via: set_memory_rox() -> change_page_attr_set_clr() -> cpa_flush() -> cpa_collapse_large_pages() Notable users of this are execmem and BPF when manipulating executable mappings. However, this is problematic for ptdump as it walks ranges it does not own and thus runs the risk of a use-after-free on page tables freed underneath it. In addition, concurrent CPA collapse operations are possible which can also cause races. Resolve the issue by acquiring the mmap write lock on init_mm across the whole operation. It is safe to acquire a sleeping lock as all the callers invoke set_memory_rox() from process context and in any case, change_page_attr_set_clr() calls vm_unmap_alias() which ultimately takes a mutex, disallowing atomic context here.

02

Engine v0.6.0

Risk summary

A use-after-free vulnerability exists in the x86 Change Page Attributes (CPA) mechanism when collapsing kernel page table entries into huge pages. The collapse operation frees underlying page tables without holding the init_mm write lock, allowing concurrent page table walkers or concurrent CPA operations to access freed memory. An attacker who can trigger set_memory_rox() — notably via BPF program loading or executable memory allocation — while racing with another operation could exploit this for kernel memory corruption, potentially leading to privilege escalation or denial of service.

Affectedarch/x86/mm/pat/set_memory.c (x86 mm/pat subsystem)

Vulnerability analysis

The x86 page attribute mechanism can collapse smaller page table entries into huge pages. During this collapse, it frees the underlying page tables without synchronizing against concurrent operations that might still be walking those tables. This allows a concurrent page table inspection or another collapse to access freed memory, resulting in a use-after-free. The corrected code now holds a global kernel memory lock across the entire collapse to exclude concurrent walkers and other collapse operations. The only way to reach this code is through a kernel routine that makes memory read-only and executable, which is used when compiling kernel programs for execution and when managing executable mappings. On systems that do not allow unprivileged use, reaching this path requires a capability equivalent to CAP_BPF.

03

BranchIntroducedFixed inPatch commit
6.186.156.18.5335820cf8dd52
7.26.157.2.793b98882198b
mainline6.157.3-rc4a1c7570cedd0