Unmount hang via terminated log-writer synchronization
Published Jun 19, 2024 · Updated May 23, 2026
A deadlock in the Linux nilfs2 log writer allows attackers to hang filesystem unmounts during teardown via unspecified vectors. nilfs_segctor_sync() attempts to synchronize with the log-writer thread after nilfs_segctor_destroy() has terminated it, leaving teardown waiting indefinitely. The path is reached when nilfs2 unmount cleanup flushes an inode that needs synchronization; the bounded consequence is a hung unmount operation.
Summary
What happened
A deadlock in the Linux nilfs2 log writer allows attackers to hang filesystem unmounts during teardown via unspecified vectors. nilfs_segctor_sync() attempts to synchronize with the log-writer thread after nilfs_segctor_destroy() has terminated it, leaving teardown waiting indefinitely. The path is reached when nilfs2 unmount cleanup flushes an inode that needs synchronization; the bounded consequence is a hung unmount operation.
The record
- CVE
- CVE-2024-38582
- Published
- Jun 19, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=28cd54f27d309bd65db8ff4b8e6275345287484c
- Affected versionversion=3.10.69 <3.11
- Affected versionversion=3.12.38 <3.13
- Affected versionversion=3.14.33 <3.15
- Affected versionversion=3.18.7 <3.19
- Affected versionversion=3.19
- Affected versionversion=3.2.68 <3.3
- Affected versionversion=3.4.107 <3.5
- Affected versionversion=52e87609d9d3ea34cadb5676e8ea85d025ac9632
- Affected versionversion=7bb9e4a06e12583f1418b669dc45bb3ee84496c6
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <6e5c8e8e024e147b834f56f2115aad241433679b
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <911d38be151921a5d152bb55e81fd752384c6830
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <a8799662fed1f8747edae87a1937549288baca6a
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3b
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <c516db6ab9eabbedbc430b4f93b0d8728e9b427f
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <eb85dace897c5986bc2f36b3c783c6abb8a4292e
- Affected versionversion=7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 <eff7cdf890b02596b8d73e910bdbdd489175dbdb
- Affected versionversion=c23f3a9fa7826af0465b9408b186f6b555991890
- Affected versionversion=d26f2dfa556323787ee1ebd5d03aeaa8650c7404
- Affected versionversion=ec7cae16b37ab478d6d7e33e8563b24ca189e6cf
What conditions does exploitation require?
What is affected?
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