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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 23.10 | noarch | linux | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure-6.5 | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-gcp | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-gcp-6.5 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-hwe-6.5 | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-laptop | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-lowlatency | < any | UNKNOWN |
git.kernel.org/linus/e3b63e966cac0bf78aaa1efede1827a252815a1d (6.8-rc6)
git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644
git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe
git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d
launchpad.net/bugs/cve/CVE-2024-26832
nvd.nist.gov/vuln/detail/CVE-2024-26832
security-tracker.debian.org/tracker/CVE-2024-26832
www.cve.org/CVERecord?id=CVE-2024-26832