mm/rmap: handle device-exclusive entries in folio_referenced_one()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9075e5fbad71e00a73cddef901a2a08ad7b51af5, Kernel f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: mm/rmap: handle device-exclusive entries in folio_referenced_one() page_vma_mapped_walk() can return non-present device-exclusive entries, but folio_referenced_one() passes them to PTE young-bit accessors that require present PTEs. We must neither call clear_flush_young_ptes_notify() nor folio_pte_batch() with non-present entries. For example, clearing the young bit on non-present PTEs can corrupt the entry: on arm64 PTE_AF overlaps the swap type, so clearing it turns a device-exclusive entry into an ordinary swap entry. folio_pte_batch() will VM_WARN_ON_FOLIO. Apply the same approach as the previous fixes to e.g., damon_ptep_mkold(): treat these entries as old from the CPU's perspective and obtain their young state through the MMU notifier. Skip PTE batching and MGLRU look-around for non-present entries, and don't modify non-present PTEs.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.14, >=b756a3b5e7ead8f6f4b03cea8ac22478ce04c8a8 <9075e5fbad71e00a73cddef901a2a08ad7b51af5, >=b756a3b5e7ead8f6f4b03cea8ac22478ce04c8a8 <f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c | 9075e5fbad71e00a73cddef901a2a08ad7b51af5, f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c |
| linux-kernel: Kernel | >=5.14.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket