CVE-2024-38582: Linux kernel · nilfs2: fix potential hang in nilfs_detach_log_writer()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 5.4.0-1130.140~18.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 10:59 UTC
- Patch
- Available – fixed in 5.4.0-1130.140~18.04.1, 5.4.0-1135.142~18.04.1, 5.4.0-1134.143~18.04.1 +73
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6979-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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().
References
- ubuntu.com/security/CVE-2024-38582 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-38582 (opens in a new tab)
- git.kernel.org/linus/eb85dace897c5986bc2f36b3c783c6abb8a4292e (opens in a new tab)
- git.kernel.org/stable/c/911d38be151921a5d152bb55e81fd752384c6830 (opens in a new tab)
- git.kernel.org/stable/c/bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3b (opens in a new tab)
- git.kernel.org/stable/c/eff7cdf890b02596b8d73e910bdbdd489175dbdb (opens in a new tab)
- git.kernel.org/stable/c/06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd (opens in a new tab)
- git.kernel.org/stable/c/1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0 (opens in a new tab)
- git.kernel.org/stable/c/a8799662fed1f8747edae87a1937549288baca6a (opens in a new tab)
- git.kernel.org/stable/c/6e5c8e8e024e147b834f56f2115aad241433679b (opens in a new tab)
- git.kernel.org/stable/c/c516db6ab9eabbedbc430b4f93b0d8728e9b427f (opens in a new tab)
- git.kernel.org/stable/c/eb85dace897c5986bc2f36b3c783c6abb8a4292e (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-2 (opens in a new tab)