CVE-2024-57952
Last modified
CVE-2024-57952 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: Revert "libfs: fix infinite directory reads for offset dir" The current directory offset allocator (based on mtree_alloc_cyclic) stores the next offset value to return in octx->next_offset. This mechanism typically returns values that increase monotonically over time. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: Revert "libfs: fix infinite directory reads for offset dir" The current directory offset allocator (based on mtree_alloc_cyclic) stores the next offset value to return in octx->next_offset. This mechanism typically returns values that increase monotonically over time. Eventually, though, the newly allocated offset value wraps back to a low number (say, 2) which is smaller than other already- allocated offset values. Yu Kuai <yukuai3@huawei.com> reports that, after commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir"), if a directory's offset allocator wraps, existing entries are no longer visible via readdir/getdents because offset_readdir() stops listing entries once an entry's offset is larger than octx->next_offset. These entries vanish persistently -- they can be looked up, but will never again appear in readdir(3) output. The reason for this is that the commit treats directory offsets as monotonically increasing integer values rather than opaque cookies, and introduces this comparison: if (dentry2offset(dentry) >= last_index) { On 64-bit platforms, the directory offset value upper bound is 2^63 - 1. Directory offsets will monotonically increase for millions of years without wrapping. On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The allocator can wrap after only a few weeks (at worst). Revert commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir") to prepare for a fix that can work properly on 32-bit systems and might apply to recent LTS kernels where shmem employs the simple_offset mechanism.
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 |
|---|---|---|
| Linux | Linux Kernel | >= 6.11, < 6.12.12 |
| Linux | Linux Kernel | 6.13 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-57952?
How severe is CVE-2024-57952?
How do I fix CVE-2024-57952?
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-57947In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57948In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57949In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5795A Denial of Service vulnerability was identified in GitHub E…6.5
- CVE-2024-57950In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57951In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-57953In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-57954Permission verification vulnerability in the media library m…7.5
- CVE-2024-57955Arbitrary write vulnerability in the Gallery module Impact:…7.5
- CVE-2024-57956Out-of-bounds read vulnerability in the interpreter string m…7.5
- CVE-2024-57957Vulnerability of improper log information control in the UI …7.5
- CVE-2024-57958Out-of-bounds array read vulnerability in the FFRT module Im…9.1
Are you affected by CVE-2024-57952?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
