First published: Wed Apr 17 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Kernel-devel | ||
Linux Kernel | >=6.1.30<6.1.80 | |
Linux Kernel | >=6.4<6.6.19 | |
Linux Kernel | >=6.7<6.7.7 | |
Linux Kernel | =6.3.4 | |
Linux Kernel | =6.8-rc1 | |
Linux Kernel | =6.8-rc2 | |
Linux Kernel | =6.8-rc3 | |
Linux Kernel | =6.8-rc4 | |
Linux Kernel | =6.8-rc5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-26832 has a medium severity rating due to potential race conditions affecting memory management.
To fix CVE-2024-26832, upgrade to the latest patched version of the Linux kernel.
CVE-2024-26832 affects versions of the Linux kernel that utilize the zswap feature.
CVE-2024-26832 may lead to instability or performance degradation if exploited.
As of now, there are no publicly known exploits for CVE-2024-26832, but it is advisable to mitigate the risk by applying updates.