CVE-2024-26630
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.6.21
- Linux Kernel < 6.7.9
- Linux Kernel 6.8
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26630.md and follow it. Check whether this project is affected by CVE-2024-26630. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804
- https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117
- https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c
- https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804
- https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117
- https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c
References
- https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804
- https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117
- https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c
- https://git.kernel.org/stable/c/3a75cb05d53f4a6823a32deb078de1366954a804
- https://git.kernel.org/stable/c/ba60fdf75e89ea762bb617be578dc47f27655117
- https://git.kernel.org/stable/c/fe7e008e0ce728252e4ec652cceebcc62211657c