Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26832mm: zswap: fix missing folio cleanup in writeback race path

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26832, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2cab13f500a6333bd2b853783ac76be9e4956f8a – < 14f1992430ef9e647b02aa8ca12c5bcb9a1dffea
    • affected 04fc7816089c5a32c29a04ec94b998e219dfb946 – < 6156277d1b26cb3fdb6fcbf0686ab78268571644
    • affected 04fc7816089c5a32c29a04ec94b998e219dfb946 – < e2891c763aa2cff74dd6b5e978411ccf0cf94abe
    • affected 04fc7816089c5a32c29a04ec94b998e219dfb946 – < e3b63e966cac0bf78aaa1efede1827a252815a1d
    • affected ba700ea13bf0105a4773c654f7d3bef8adb64ab2
    • affected 6.1.30 – < 6.1.80
    • affected 6.3.4 – < 6.4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.1.80 – ≤ 6.1.*
    • unaffected 6.6.19 – ≤ 6.6.*
    • unaffected 6.7.7 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26832 badge
[![CVE-2024-26832](https://cveledger.app/badge/CVE-2024-26832.svg)](https://cveledger.app/cve/CVE-2024-26832)

Record last updated .