mm: filemap: retain mapped dropbehind folios
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2897601dffe576fcd87a4259102f41f7fb0cbfc8, Kernel 77c0fade37c80e8aa16ac048a9828249055e3f66 and Kernel 848d2ce2fce15fbdc083fbf9691bfa72911033c4.
In the Linux kernel, the following vulnerability has been resolved: mm: filemap: retain mapped dropbehind folios Fault-around can map ready dropbehind folios without going through the normal page-cache lookup that clears dropbehind. A mapping represents a competing cached user, so retain the folio instead of forcibly unmapping it when writeback completes. For a mapped folio, folio_unmap_invalidate() can call unmap_mapping_folio(), which takes i_mmap_rwsem and may sleep. Retaining mapped folios avoids this path when folio_end_dropbehind() runs in non-preemptible task context. Tal was able to trigger a sleeping-in-atomic warning due to this [1]. Unmapped dropbehind folios continue through the existing invalidation path.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=fb7d3bc4149395c1ae99029c852eab6c28fc3c88 <2897601dffe576fcd87a4259102f41f7fb0cbfc8, >=fb7d3bc4149395c1ae99029c852eab6c28fc3c88 <77c0fade37c80e8aa16ac048a9828249055e3f66, >=fb7d3bc4149395c1ae99029c852eab6c28fc3c88 <848d2ce2fce15fbdc083fbf9691bfa72911033c4 | 2897601dffe576fcd87a4259102f41f7fb0cbfc8, 77c0fade37c80e8aa16ac048a9828249055e3f66, 848d2ce2fce15fbdc083fbf9691bfa72911033c4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket