System hang via locked OCFS2 symlink page
Published Feb 27, 2025 · Updated May 11, 2026
Denial of service in the Linux kernel's OCFS2 symlink reader allows local users to hang affected systems through a read error. The error path in fs/ocfs2/symlink.c returns after a buffer-read failure without unlocking the associated page, leaving it permanently locked. Exploitation requires low-privileged local access and a mounted OCFS2 filesystem where a symlink read can enter that failure path; the resulting impact is limited to availability.
Summary
What happened
Denial of service in the Linux kernel's OCFS2 symlink reader allows local users to hang affected systems through a read error. The error path in fs/ocfs2/symlink.c returns after a buffer-read failure without unlocking the associated page, leaving it permanently locked. Exploitation requires low-privileged local access and a mounted OCFS2 filesystem where a symlink read can enter that failure path; the resulting impact is limited to availability.
The record
- CVE
- CVE-2024-58001
- Published
- Feb 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.
- Affected versionversion=3.5
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <2b4c2094da6d84e69b843dd3317902e977bf64bd
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <52a326f93ceb9348264fddf7bab6e345db69e08c
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <5e3b3ec7c3cb5ba5629a766e4f0926db72cf0a1f
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <6e143eb4ab83c24e7ad3e3d8e7daa241d9c38377
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <8aee4184c5b79e486598c15aa80687c77f6f6e6e
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <afa8003f8db62e46c4b171cbf4cec2824148b4f7
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <b6833b38984d1e9f20dd80f9ec9050c10d687f30
- Affected versionversion=ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1 <cd3e22b206189cbb4a94229002141e1529f83746
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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