Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-57952 — kernel

🟠 CVSS 7.1 — High ✅ No Known Exploit NVD
7.1
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Revert "libfs: fix infinite directory reads for offset dir"

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 <[email protected]> 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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-57952 is recorded against 2 packages.

  • kernel (from 6.13.0 up to 6.13.1)
  • linux-kernel

Timeline and source

Published on 12 February 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity High
CVSS Score 7.1
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-02-12
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.13.0 6.13.1
linux-kernel — —

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2024-57952 is rated CVSS 7.1 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓