LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57942: netfs: Fix ceph copy to cache on write-begin

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix ceph copy to cache on write-begin At the end of netfs_unlock_read_folio() in which folios are marked appropriately for copying to the cache (either with by being marked dirty and having their private data set or by having PG_private_2 set) and then unlocked, the folio_queue struct has the entry pointing to the folio cleared. This presents a problem for netfs_pgpriv2_write_to_the_cache(), which is used to write folios marked with PG_private_2 to the cache as it expects to be able to trawl the folio_queue list thereafter to find the relevant folios, leading to a hang. Fix this by not clearing the folio_queue entry if we're going to do the deprecated copy-to-cache. The clearance will be done instead as the folios are written to the cache. This can be reproduced by starting cachefiles, mounting a ceph filesystem with "-o fsc" and writing to it.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can hang systems using Ceph filesystem caching. The described trigger requires cachefiles, a Ceph mount using the fsc option, and writes to that filesystem. The main business risk is availability disruption on affected Linux hosts that rely on cached Ceph storage.

Executive priority

Treat this as a targeted availability risk for Ceph-backed Linux infrastructure, not an internet-wide emergency. Patch on the normal urgent infrastructure cycle if cached Ceph clients are in production; otherwise track through routine kernel maintenance.

Technical view

The bug is in netfs/Ceph copy-to-cache handling during write-begin. netfs_unlock_read_folio() clears folio_queue entries too early, while netfs_pgpriv2_write_to_the_cache() later expects those entries to locate PG_private_2 folios. The result is a hang. Stable kernel commits change queue clearing behavior for the deprecated copy-to-cache path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with Ceph filesystem caching enabled through cachefiles and a Ceph mount using -o fsc. General Linux systems without this storage path are not shown as exposed by the provided sources.

Exploitation context

The sources provide a reproduction condition but no evidence of active exploitation, public weaponization, or KEV listing. This looks like an availability bug reachable through a specific configured storage workflow, not a broadly exposed remote vulnerability based on the supplied evidence.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. No CVSS, CWE, exploit status, or distro-specific package data is supplied. The described impact is a hang in a specific netfs/Ceph cache interaction.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Prioritize hosts using Ceph filesystem caching with cachefiles and -o fsc.
  • Check Linux distribution advisories for exact fixed package versions.
  • Temporarily avoid the Ceph fsc caching path where operationally acceptable.
  • Validate storage workloads after patching to confirm hangs do not recur.

Validation and detection

  • Inventory Linux kernel versions on Ceph client hosts.
  • Identify hosts running cachefiles with Ceph mounts using the fsc option.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review logs and monitoring for hangs during cached Ceph writes.
  • Run regression testing for representative Ceph write workloads after updating.
Prepared
Confidence
medium
Sources
4

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-57942 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
0ADP providers
3Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxee4cdf7ba857a894ad1650d6ab77669cbbfa329e, ee4cdf7ba857a894ad1650d6ab77669cbbfa329eunaffected
LinuxLinux6.12, 0, 6.12.10, 6.13affected
Weakness

CWE details

No CWE listed

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