CVE-2024-38582: nilfs2: fix potential hang in nilfs_detach_log_writer()
First published: Wed Jun 19 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential hang in nilfs_detach_log_writer() Syzbot has reported a potential hang in nilfs_detach_log_writer() called during nilfs2 unmount. Analysis revealed that this is because nilfs_segctor_sync(), which synchronizes with the log writer thread, can be called after nilfs_segctor_destroy() terminates that thread, as shown in the call trace below: nilfs_detach_log_writer nilfs_segctor_destroy nilfs_segctor_kill_thread --> Shut down log writer thread flush_work nilfs_iput_work_func nilfs_dispose_list iput nilfs_evict_inode nilfs_transaction_commit nilfs_construct_segment (if inode needs sync) nilfs_segctor_sync --> Attempt to synchronize with log writer thread *** DEADLOCK *** Fix this issue by changing nilfs_segctor_sync() so that the log writer thread returns normally without synchronizing after it terminates, and by forcing tasks that are already waiting to complete once after the thread terminates. The skipped inode metadata flushout will then be processed together in the subsequent cleanup work in nilfs_segctor_destroy().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.16-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd
- https://git.kernel.org/stable/c/1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0
- https://git.kernel.org/stable/c/6e5c8e8e024e147b834f56f2115aad241433679b
- https://git.kernel.org/stable/c/911d38be151921a5d152bb55e81fd752384c6830
- https://git.kernel.org/stable/c/a8799662fed1f8747edae87a1937549288baca6a
- https://git.kernel.org/stable/c/bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3b
- https://git.kernel.org/stable/c/c516db6ab9eabbedbc430b4f93b0d8728e9b427f
- https://git.kernel.org/stable/c/eb85dace897c5986bc2f36b3c783c6abb8a4292e
- https://git.kernel.org/stable/c/eff7cdf890b02596b8d73e910bdbdd489175dbdb
- https://launchpad.net/bugs/cve/CVE-2024-38582
- https://git.kernel.org/linus/eb85dace897c5986bc2f36b3c783c6abb8a4292e
- https://security-tracker.debian.org/tracker/CVE-2024-38582
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38582
- https://nvd.nist.gov/vuln/detail/CVE-2024-38582
- https://ubuntu.com/security/CVE-2024-38582
Frequently Asked Questions
What is the severity of CVE-2024-38582?
CVE-2024-38582 has a severity rating that indicates it can lead to potential hangs during the unmount process in nilfs2, affecting system stability.
How do I fix CVE-2024-38582?
To fix CVE-2024-38582, update to the fixed versions of the Linux kernel: 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.13-1.
What versions of the Linux kernel are affected by CVE-2024-38582?
CVE-2024-38582 affects multiple versions of the Linux kernel, specifically those prior to 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, and 6.12.13-1.
What is the impact of CVE-2024-38582?
The impact of CVE-2024-38582 can result in system hangs when attempting to detach log writers during the unmount process of nilfs2.
Who reported the issue related to CVE-2024-38582?
The issue related to CVE-2024-38582 was reported by Syzbot, which is an automated bug detection tool.
- agent/title
- agent/type
- collector/launchpad-cve
- source/Launchpad
- agent/remedy
- agent/author
- agent/first-publish-date
- agent/references
- collector/nvd-api
- source/NVD
- agent/severity
- agent/description
- collector/nvd-cve
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- package-manager/debian