Service interruption via SysV filesystem lock misuse
Published May 19, 2024 · Updated May 11, 2026
Improper locking in the Linux SysV filesystem on affected kernels allows attackers to interrupt service during filesystem block reads. The fs/sysv/itree.c path calls sb_bread(), which can sleep, while pointers_lock is held as a read-write spinlock, creating an atomic-context locking fault. The vulnerable path requires SysV filesystem I/O; published sources do not specify the access needed to trigger it.
Summary
What happened
Improper locking in the Linux SysV filesystem on affected kernels allows attackers to interrupt service during filesystem block reads. The fs/sysv/itree.c path calls sb_bread(), which can sleep, while pointers_lock is held as a read-write spinlock, creating an atomic-context locking fault. The vulnerable path requires SysV filesystem I/O; published sources do not specify the access needed to trigger it.
The record
- CVE
- CVE-2023-52699
- Published
- May 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2024CVE 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <13b33feb2ebddc2b1aa607f553566b18a4af1d76
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cb1e52c9db618c08335984d1ca80db220ccf09
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <674c1c4229e743070e09db63a23442950ff000d1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <89e8524135a3902e7563a5a59b7b5ec1bf4904ac
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a69224223746ab96d43e5db9d22d136827b7e2d3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f123dc86388cb669c3d6322702dc441abc35c31e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd203d2c671bdee9ab77090ff394d3b71b627927
- Affected versionversion=2.6.12
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