CVE-2024-26832: mm: zswap: fix missing folio cleanup in writeback race path
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: fix missing folio cleanup in writeback race path
In zswapwritebackentry(), after we get a folio from readswapcacheasync(), 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, readswapcacheasync() 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 Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-26832?
CVE-2024-26832 has a medium severity rating due to potential race conditions affecting memory management.
How do I fix CVE-2024-26832?
To fix CVE-2024-26832, upgrade to the latest patched version of the Linux kernel.
What systems are affected by CVE-2024-26832?
CVE-2024-26832 affects versions of the Linux kernel that utilize the zswap feature.
What impact does CVE-2024-26832 have on system performance?
CVE-2024-26832 may lead to instability or performance degradation if exploited.
Is there a known exploit for CVE-2024-26832?
As of now, there are no publicly known exploits for CVE-2024-26832, but it is advisable to mitigate the risk by applying updates.