LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26630: mm: cachestat: fix folio read-after-free in cache walk

In the Linux kernel, the following vulnerability has been resolved: mm: cachestat: fix folio read-after-free in cache walk In cachestat, we access the folio from the page cache's xarray to compute its page offset, and check for its dirty and writeback flags. However, we do not hold a reference to the folio before performing these actions, which means the folio can concurrently be released and reused as another folio/page/slab. Get around this altogether by just using xarray's existing machinery for the folio page offsets and dirty/writeback states. This changes behavior for tmpfs files to now always report zeroes in their dirty and writeback counters. This is okay as tmpfs doesn't follow conventional writeback cache behavior: its pages get "cleaned" during swapout, after which they're no longer resident etc.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel memory-management race can make the cachestat cache-walking code use memory after it has been freed and reassigned. A local, low-privileged user could potentially expose sensitive information or crash the system. The supplied evidence does not show remote reachability or active exploitation.

Executive priority

Treat this as a high-priority kernel maintenance issue, especially for shared servers, developer platforms, and systems executing untrusted workloads. It is not supported as an internet-wide emergency because attack access is local and active exploitation is unconfirmed. Obtain vendor-specific package guidance promptly.

Technical view

Cachestat reads a folio from the page-cache xarray without holding a reference. Concurrent release and reuse can therefore produce a read-after-free while calculating offsets or checking dirty and writeback state. The cited fixes use existing xarray metadata instead. The change intentionally makes tmpfs dirty and writeback counters report zero.

Likely exposure

Systems running affected Linux kernels and allowing untrusted local code are the primary concern. The bundle lists 6.5, 6.6.21, 6.7.9, and 6.8, plus ambiguous commit and “0” entries; it does not clearly define complete version ranges. Distribution backports may alter exposure.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction, with potentially high confidentiality and availability impact. KEV is false, and the supplied sources provide no evidence of active exploitation, public exploit availability, or remote attackability.

Researcher notes

The source describes a race-dependent folio read-after-free but provides no CWE, proof of concept, exploitation telemetry, or complete affected-version boundaries. Assessment should distinguish upstream versions from distribution kernels with backports. The tmpfs counter behavior change is documented as an accepted consequence of the fix.

Mitigation direction

  • Upgrade to a vendor-supported Linux kernel containing an applicable cited stable fix.
  • Check distribution security guidance for backported fixes and exact package versions.
  • Prioritize multi-user systems and hosts running untrusted local workloads.
  • Reduce untrusted local code execution where feasible until affected systems are patched.

Validation and detection

  • Inventory running kernel and distribution package versions across Linux systems.
  • Compare each package with vendor advisories and the cited stable-kernel fixes.
  • Confirm the corrected kernel is running after maintenance or reboot.
  • Review kernel crash telemetry, recognizing the bundle provides no reliable exploitation indicator.
Prepared
Confidence
medium
Sources
5

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-26630 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2024-26630Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinuxcf264e1329fb0307e044f7675849f9f38b44c11a, cf264e1329fb0307e044f7675849f9f38b44c11a, cf264e1329fb0307e044f7675849f9f38b44c11aunaffected
LinuxLinux6.5, 0, 6.6.21, 6.7.9, 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.