LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57941: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled When the caching for a cookie is temporarily disabled (e.g. due to a DIO write on that file), future copying to the cache for that file is disabled until all fds open on that file are closed. However, if netfslib is using the deprecated PG_private_2 method (such as is currently used by ceph), and decides it wants to copy to the cache, netfs_advance_write() will just bail at the first check seeing that the cache stream is unavailable, and indicate that it dealt with all the content. This means that we have no subrequests to provide notifications to drive the state machine or even to pin the request and the request just gets discarded, leaving the folios with PG_private_2 set. Fix this by jumping directly to cancel the request if the cache is not available. That way, we don't remove mark3 from the folio_queue list and netfs_pgpriv2_cancel() will clean up the folios. This was found by running the generic/013 xfstest against ceph with an active cache and the "-o fsc" option passed to ceph. That would usually hang

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leave file-cache state uncleared when netfs caching is temporarily unavailable. The reported effect is a hang during Ceph filesystem testing with fscache enabled. The sources do not provide CVSS, confirmed real-world exploitation, or a broad impact assessment.

Executive priority

Track for routine-to-expedited kernel maintenance where Ceph fscache is used. Escalate if affected systems support critical availability requirements or show filesystem hangs. Current public evidence does not justify emergency treatment on exploitation grounds.

Technical view

In netfs, when cache copying is disabled and the deprecated PG_private_2 path is used, netfs_advance_write() can exit without creating subrequests or cancelling the request. Folios may retain PG_private_2, causing the state machine cleanup to stall. The fix cancels the request when the cache stream is unavailable.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with netfs/fscache behavior, especially Ceph with the -o fsc option. The bundle lists Linux 6.12, 6.12.10, and 6.13-related version data, but exact deployment exposure should be verified against vendor kernel advisories.

Exploitation context

The source describes discovery through generic/013 xfstest against Ceph with active cache. KEV is false, and the provided sources do not state active exploitation or public weaponization. Treat this as a reliability and availability concern unless vendor guidance says otherwise.

Researcher notes

Key condition is unavailable cache stream with deprecated PG_private_2 handling. The bug path fails to generate cleanup-driving subrequests, leaving marked folios. Source evidence is strongest for Ceph with active cache during xfstest generic/013; broader filesystem impact is not established in the bundle.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-57941 kernel update status.
  • Prioritize affected Ceph clients using fscache or -o fsc.
  • Apply vendor kernel updates that include the referenced stable fixes.
  • If patching is delayed, review vendor guidance on disabling affected caching paths.
  • Avoid inventing compensating controls beyond documented vendor recommendations.

Validation and detection

  • Inventory Linux kernel versions on Ceph and netfs/fscache clients.
  • Identify workloads using Ceph with fscache enabled.
  • Confirm whether kernel packages include the referenced stable commits.
  • Review system logs for Ceph or netfs hangs under cached IO workloads.
  • Run regression tests only in controlled environments, not production.
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-57941 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.