CVE-2024-53685: ceph: give up on paths longer than PATH_MAX
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0f2b2d9e881c90402dbe28f9ba831775b7992e1f, 550f7ca98ee028a606aa75705a7e77b1bd11720f, 99a37ab76a315c8307eb5b0dc095d8ad9d8efeaa.
Low priority for now. Upgrade to Linux Linux 0f2b2d9e881c90402dbe28f9ba831775b7992e1f, 550f7ca98ee028a606aa75705a7e77b1bd11720f, 99a37ab76a315c8307eb5b0dc095d8ad9d8efeaa or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ceph: give up on paths longer than PATH_MAX If the full path to be built by ceph_mdsc_build_path() happens to be longer than PATH_MAX, then this function will enter an endless (retry) loop, effectively blocking the whole task. Most of the machine becomes unusable, making this a very simple and effective DoS vulnerability. I cannot imagine why this retry was ever implemented, but it seems rather useless and harmful to me. Let's remove it and fail with ENAMETOOLONG instead.
- Published
- Jan 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-835
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.35 and later · before 5.10.234
- linux linux kernel5.11 and later · before 5.15.177
- linux linux kernel5.16 and later · before 6.1.125
- linux linux kernel6.2 and later · before 6.6.70
- linux linux kernel6.7 and later · before 6.12.7
- linux linux kernel2.6.34
- linux linux kernel6.13
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.34affected
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before 0f2b2d9e881c90402dbe28f9ba831775b7992e1faffected · git
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before d42ad3f161a5a487f81915c406f46943c7187a0aaffected · git
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before e4b168c64da06954be5d520f6c16469b1cadc069affected · git
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before c47ed91156daf328601d02b58d52d9804da54108affected · git
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before 99a37ab76a315c8307eb5b0dc095d8ad9d8efeaaaffected · git
- 9030aaf9bf0a1eee47a154c316c789e959638b0f and later · before 550f7ca98ee028a606aa75705a7e77b1bd11720faffected · git
- before 2.6.34not affected · semver
- 5.10.234 and later · up to and including 5.10.*not affected · semver
- 5.15.177 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
+53
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53680Jan 11, 2025 · ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init()22Monitor
- ← EarlierCVE-2024-53682Jan 11, 2025 · regulator: axp20x: AXP717: set ramp_delay22Monitor
- Later →CVE-2024-53687Jan 11, 2025 · riscv: Fix IPIs usage in kfence_protect_page()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f2b2d9e881c90402dbe28f9ba831775b7992e1f | Vendor (CNA) |
| Linux Linux | 550f7ca98ee028a606aa75705a7e77b1bd11720f | Vendor (CNA) |
| Linux Linux | 99a37ab76a315c8307eb5b0dc095d8ad9d8efeaa | Vendor (CNA) |
| Linux Linux | c47ed91156daf328601d02b58d52d9804da54108 | Vendor (CNA) |
| Linux Linux | d42ad3f161a5a487f81915c406f46943c7187a0a | Vendor (CNA) |
| Linux Linux | e4b168c64da06954be5d520f6c16469b1cadc069 | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.128-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31448466 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-52933529 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()31Monitor
- CVE-2026-23451447 days apartbonding: prevent potential infinite loop in bond_header_parse()30Monitor
- CVE-2026-31552468 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- CVE-2026-46052501 days apartceph: only d_add() negative dentries when they are unhashed30Monitor
- CVE-2024-27032255 days apartf2fs: fix to avoid potential panic during recovery25Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/550f7ca98ee028a606aa75705a7e77b1bd11720f
- git.kernel.org/stable/c/99a37ab76a315c8307eb5b0dc095d8ad9d8efeaa
- git.kernel.org/stable/c/c47ed91156daf328601d02b58d52d9804da54108
- git.kernel.org/stable/c/d42ad3f161a5a487f81915c406f46943c7187a0a
- git.kernel.org/stable/c/e4b168c64da06954be5d520f6c16469b1cadc069
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.