mm/madvise: fix data loss from MADV_FREE on a KSM page
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel af2feafb0437fab5ed9d02eeb1c06ef66e05c55a, Kernel 22d043c1da48d6c7274f9dd900714b6d58b7b9c6, Kernel 64f273b71bf714dd22b803a87d65bb40faaffcad and 4 more.
In the Linux kernel, the following vulnerability has been resolved: mm/madvise: fix data loss from MADV_FREE on a KSM page MADV_FREE can clear the dirty flag of a singly mapped KSM folio. The folio remains in the stable tree and can gain new mappings without being dirtied again. Once marked lazyfree, reclaim can discard data that those mappings still need. KSM always marks a folio dirty when converting it to a KSM folio in try_to_merge_one_page(). Marking a folio lazyfree clears PG_swapbacked but leaves PG_dirty unchanged. Preserving PG_dirty makes reclaim restore PG_swapbacked instead of discarding the folio. This also protects folios that were already lazyfree when KSM converted them. Skip KSM folios before clearing their dirty flag, checking under the folio lock to serialize with KSM conversion.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9 <af2feafb0437fab5ed9d02eeb1c06ef66e05c55a, >=854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9 <22d043c1da48d6c7274f9dd900714b6d58b7b9c6, >=854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9 <64f273b71bf714dd22b803a87d65bb40faaffcad, >=854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9 <8b6860f17b4de23a0b19045c066dc0679e50f0ba, =4.5 | af2feafb0437fab5ed9d02eeb1c06ef66e05c55a, 22d043c1da48d6c7274f9dd900714b6d58b7b9c6, 64f273b71bf714dd22b803a87d65bb40faaffcad, 8b6860f17b4de23a0b19045c066dc0679e50f0ba |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=4.5.0 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket