x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.537.2.77.3In the Linux kernel, the following vulnerability has been resolved:
x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF
A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked).
When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic():
... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic()
There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free.
With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().
This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race.
From the CVE record · Linux
The Linux kernel’s x86 page-attribute code has a race between attribute changes and concurrent page-table collapse that can cause a use-after-free. The input does not specify how an attacker could trigger the race or whether access or user interaction is required.
Engineers running the Linux kernel on x86 systems should check their kernel versions; affected versions are not specified.