CVE-2024-57952

Persistent directory-entry hiding via offset wraparound

Published Feb 12, 2025 · Updated Aug 5, 2026

Directory-offset handling in affected Linux kernels allows local users to persistently hide existing entries from directory listings. After a 32-bit offset allocator wraps, offset_readdir() compares opaque directory cookies as monotonic integers and stops at an entry whose offset is at least octx->next_offset. The flaw requires local low-privilege access and enough offset allocations to force 32-bit wraparound; entries remain addressable but disappear from readdir/getdents output.

CVSS severity7.1
High
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Directory-offset handling in affected Linux kernels allows local users to persistently hide existing entries from directory listings. After a 32-bit offset allocator wraps, offset_readdir() compares opaque directory cookies as monotonic integers and stops at an entry whose offset is at least octx->next_offset. The flaw requires local low-privilege access and enough offset allocations to force 32-bit wraparound; entries remain addressable but disappear from readdir/getdents output.

The record

CVE
CVE-2024-57952
Published
Feb 12, 2025
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 12, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=308b4fc2403b335894592ee9dc212a5e58bb309f
  2. Affected versionversion=6.10.7 <6.11
  3. Affected versionversion=6.11
  4. Affected versionversion=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <3f250b82040a72b0059ae00855a74d8570ad2147
  5. Affected versionversion=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <9e9e710f68bac49bd9b587823c077d06363440e0
  6. Affected versionversion=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <b662d858131da9a8a14e68661656989b14dbf113

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=308b4fc2403b335894592ee9dc212a5e58bb309f; version=6.10.7 <6.11; version=6.11; version=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <3f250b82040a72b0059ae00855a74d8570ad2147; version=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <9e9e710f68bac49bd9b587823c077d06363440e0; version=64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a <b662d858131da9a8a14e68661656989b14dbf113

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
7.1kernel.orgCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo