CVE-2024-26832
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-459
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.80
- Linux Kernel < 6.6.19
- Linux Kernel < 6.7.7
- Linux Kernel 6.3.4
- Linux Kernel 6.8
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26832.md and follow it. Check whether this project is affected by CVE-2024-26832. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
- https://git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644
- https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe
- https://git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d
- https://git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
- https://git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644
- https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe
- https://git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d
References
- https://git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
- https://git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644
- https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe
- https://git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d
- https://git.kernel.org/stable/c/14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
- https://git.kernel.org/stable/c/6156277d1b26cb3fdb6fcbf0686ab78268571644
- https://git.kernel.org/stable/c/e2891c763aa2cff74dd6b5e978411ccf0cf94abe
- https://git.kernel.org/stable/c/e3b63e966cac0bf78aaa1efede1827a252815a1d