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.
History

Thu, 19 Dec 2024 09:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2024-04-17T10:10:01.016Z

Updated: 2024-12-19T08:48:18.069Z

Reserved: 2024-02-19T14:20:24.181Z

Link: CVE-2024-26832

cve-icon Vulnrichment

Updated: 2024-08-02T00:14:13.535Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-04-17T10:15:09.507

Modified: 2024-11-21T09:03:10.120

Link: CVE-2024-26832

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-04-17T00:00:00Z

Links: CVE-2024-26832 - Bugzilla