CVE-2024-57952: Linux kernel · Revert "libfs: fix infinite directory reads for offset dir
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1030.32~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1030.32~22.04.1, 6.8.0-1030.35~22.04.1, 6.8.0-1031.33~22.04.1 +31
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux@6.8.0-62.65?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws@6.8.0-1030.32?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure@6.8.0-1030.35?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11@6.11.0-1013.13~24.04.1?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia@6.8.0-1018.19?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp@6.8.0-1031.33?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-57952 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-57952 (opens in a new tab)
- git.kernel.org/linus/b662d858131da9a8a14e68661656989b14dbf113 (opens in a new tab)
- git.kernel.org/stable/c/3f250b82040a72b0059ae00855a74d8570ad2147 (opens in a new tab)
- git.kernel.org/stable/c/9e9e710f68bac49bd9b587823c077d06363440e0 (opens in a new tab)
- git.kernel.org/stable/c/b662d858131da9a8a14e68661656989b14dbf113 (opens in a new tab)
- ubuntu.com/security/notices/USN-7445-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7448-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7595-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7596-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7595-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7596-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7595-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7595-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7595-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7653-1 (opens in a new tab)