filemap: replace pte_offset_map() with pte_offset_map_nolock()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 24be02a42181f0707be0498045c4c4b13273b16d and Kernel 6a6c2aec1a89506595801b4cf7e8eef035f33748.
In the Linux kernel, the following vulnerability has been resolved: filemap: replace pte_offset_map() with pte_offset_map_nolock() The vmf->ptl in filemap_fault_recheck_pte_none() is still set from handle_pte_fault(). But at the same time, we did a pte_unmap(vmf->pte). After a pte_unmap(vmf->pte) unmap and rcu_read_unlock(), the page table may be racily changed and vmf->ptl maybe fails to protect the actual page table. Fix this by replacing pte_offset_map() with pte_offset_map_nolock(). As David said, the PTL pointer might be stale so if we continue to use it infilemap_fault_recheck_pte_none(), it might trigger UAF. Also, if the PTL fails, the issue fixed by commit 58f327f2ce80 ("filemap: avoid unnecessary major faults in filemap_fault()") might reappear.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=58f327f2ce80f9c7b4a70e9cf017ae8810d44a20 <24be02a42181f0707be0498045c4c4b13273b16d, >=58f327f2ce80f9c7b4a70e9cf017ae8810d44a20 <6a6c2aec1a89506595801b4cf7e8eef035f33748 | 24be02a42181f0707be0498045c4c4b13273b16d, 6a6c2aec1a89506595801b4cf7e8eef035f33748 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket