CVE-2024-26630
mm: cachestat: fix folio read-after-free in cache walk
Description
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.
INFO
Published Date :
March 13, 2024, 4:15 p.m.
Last Modified :
March 13, 2025, 7:36 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the Linux kernel to a patched version.
- Reboot the system after the update.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-26630.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-26630 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-26630
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-26630 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-26630 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 13, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Added CWE CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.8:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.8:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.8:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.5 from (excluding) 6.6.21 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 from (excluding) 6.7.9 Added Reference Type CVE: https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804 Added Reference https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117 Added Reference https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 13, 2024
Action Type Old Value New Value Added Description 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. Added Reference Linux https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804 [No types assigned]