cbcvebase.
CVE-2024-57952
published 2025-02-12

CVE-2024-57952: In the Linux kernel, the following vulnerability has been resolved: Revert "libfs: fix infinite directory reads for offset dir" The current directory offset…

PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.8th percentile
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 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.

Affected

19 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.12.12-1 (forky)linux 6.12.12-1 (forky)
linuxlinux
linuxlinux
linuxlinux>= 6.10.7 < 6.116.11
linuxlinux>= 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a < 9e9e710f68bac49bd9b587823c077d06363440e09e9e710f68bac49bd9b587823c077d06363440e0
linuxlinux>= 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a < 3f250b82040a72b0059ae00855a74d8570ad21473f250b82040a72b0059ae00855a74d8570ad2147
linuxlinux>= 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a < b662d858131da9a8a14e68661656989b14dbf113b662d858131da9a8a14e68661656989b14dbf113
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.12.12-16.12.12-1
linuxlinux_kernel>= 0 < 6.12.12-16.12.12-1
linuxlinux_kernel>= 0 < 6.8.0-62.656.8.0-62.65
linuxlinux_kernel>= 6.11 < 6.12.126.12.12

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.9MEDIUM
vendor_ubuntu5.9MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.