CVE-2024-35872
Last modified
CVE-2024-35872 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mm/secretmem: fix GUP-fast succeeding on secretmem folios folio_is_secretmem() currently relies on secretmem folios being LRU folios, to save some cycles. However, folios might reside in a folio batch without the LRU flag set, or temporarily have their LRU flag cleared. Consequently, the LRU flag is unreliable for this purpose. In particular, this is the case when secretmem_fault() allocates a fresh page and calls filemap_add_folio()->folio_add_lru(). EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/secretmem: fix GUP-fast succeeding on secretmem folios folio_is_secretmem() currently relies on secretmem folios being LRU folios, to save some cycles. However, folios might reside in a folio batch without the LRU flag set, or temporarily have their LRU flag cleared. Consequently, the LRU flag is unreliable for this purpose. In particular, this is the case when secretmem_fault() allocates a fresh page and calls filemap_add_folio()->folio_add_lru(). The folio might be added to the per-cpu folio batch and won't get the LRU flag set until the batch was drained using e.g., lru_add_drain(). Consequently, folio_is_secretmem() might not detect secretmem folios and GUP-fast can succeed in grabbing a secretmem folio, crashing the kernel when we would later try reading/writing to the folio, because the folio has been unmapped from the directmap. Fix it by removing that unreliable check.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.14, < 5.15.154 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.85 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.26 | — |
| Linux | Linux Kernel | >= 6.7, < 6.8.5 | — |
| Linux | Linux Kernel | 6.9 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-35872?
How severe is CVE-2024-35872?
How do I fix CVE-2024-35872?
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-35867In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-35868In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-35869In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2024-3587The Premium Portfolio Features for Phlox theme plugin for Wo…5.4
- CVE-2024-35870In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2024-35871In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-35873In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35874In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35875In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35876Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-35877In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35878In the Linux kernel, the following vulnerability has been re…5.3
Are you affected by CVE-2024-35872?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
