CVE-2024-26630
Last modified
CVE-2024-26630 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.5, < 6.6.21 | — |
| Linux | Linux Kernel | >= 6.7, < 6.7.9 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-26630?
How severe is CVE-2024-26630?
How do I fix CVE-2024-26630?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-26625In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26626In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26627In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26628Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-26629In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2663The ZD YouTube FLV Player plugin for WordPress is vulnerable…8.3
- CVE-2024-26631In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-26632In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26633In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26634In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26635In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26636In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-26630?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
