LiveActive security incident?Get immediate response
CVE Record

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 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leak a memory page reference during a rare zswap writeback race. The source says it was found by code inspection and would not crash the system, but could strand a folio indefinitely. Business impact appears operational rather than immediate compromise.

Executive priority

Handle through normal kernel maintenance unless the environment is highly sensitive to memory pressure or runs large zswap-enabled Linux fleets. There is no source evidence of exploitation or privilege-impacting behavior.

Technical view

In zswap_writeback_entry(), a newly allocated folio from __read_swap_cache_async() can remain locked and referenced when the swap entry was invalidated and recycled. The resolved fix unlocks and puts the folio before returning in that race path.

Likely exposure

Exposure is limited to Linux systems using affected kernel builds with zswap writeback behavior. The bundle identifies Linux kernel as the affected product and references stable kernel fixes, but does not provide distribution-specific package names.

Exploitation context

The bundle reports no KEV listing and no active exploitation evidence. The description says the path handles an uncommon race, was found by code inspection, and the observed consequence is stranded folios rather than system crash.

Researcher notes

The evidence points to a cleanup bug in a rare invalidation/recycle race in zswap writeback. The source does not provide CVSS, CWE, exploitability analysis, or distribution package mapping, so validation should focus on kernel provenance and fix inclusion.

Mitigation direction

  • Update affected Linux kernels using vendor or distribution guidance.
  • Prioritize kernel.org stable fixes or downstream packages containing the referenced commits.
  • Check whether zswap is enabled on relevant Linux fleets.
  • Track distribution advisories for exact fixed package versions.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Compare running kernels against vendor advisories for CVE-2024-26832.
  • Confirm patched kernels include one of the referenced stable commits.
  • Review memory pressure monitoring for unexplained zswap-related resource retention.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26832 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2cab13f500a6333bd2b853783ac76be9e4956f8a, 04fc7816089c5a32c29a04ec94b998e219dfb946, 04fc7816089c5a32c29a04ec94b998e219dfb946, 04fc7816089c5a32c29a04ec94b998e219dfb946, ba700ea13bf0105a4773c654f7d3bef8adb64ab2, 6.1.30, 6.3.4unaffected
LinuxLinux6.4, 0, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.