Description
In the Linux kernel, the following vulnerability has been resolved: mm: zswap: fix missing folio cleanup in writeback race path In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit. However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning. This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
2cab13f500a6333bd2b853783ac76be9e4956f8a to < 14f1992430ef9e647b02aa8ca12c5bcb9a1dffeaaffected04fc7816089c5a32c29a04ec94b998e219dfb946 to < 6156277d1b26cb3fdb6fcbf0686ab78268571644affected04fc7816089c5a32c29a04ec94b998e219dfb946 to < e2891c763aa2cff74dd6b5e978411ccf0cf94abeaffected04fc7816089c5a32c29a04ec94b998e219dfb946 to < e3b63e966cac0bf78aaa1efede1827a252815a1daffectedba700ea13bf0105a4773c654f7d3bef8adb64ab2affected6.1.30 to < 6.1.80affected6.3.4 to < 6.4affected
Linux Linux
Default version status: affected
6.4affected0 to < 6.4unaffected6.1.80 to ≤ 6.1.*unaffected6.6.19 to ≤ 6.6.*unaffected6.7.7 to ≤ 6.7.*unaffected6.8 to ≤ *unaffected