cbcvebase.
CVE-2024-38582
published 2024-06-19

CVE-2024-38582: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential hang in nilfs_detach_log_writer() Syzbot has reported a potential…

PriorityP424medium5.3CVSS 3.1
AVNACLPRNUINSUCNINAL
EPSS
0.86%
55.0th percentile
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().

Affected

38 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.94-1 (bookworm)linux 6.1.94-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 3.10.69 < 3.113.11
linuxlinux>= 3.12.38 < 3.133.13
linuxlinux>= 3.14.33 < 3.153.15
linuxlinux>= 3.18.7 < 3.193.19
linuxlinux>= 3.2.68 < 3.33.3
linuxlinux>= 3.4.107 < 3.53.5
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < 911d38be151921a5d152bb55e81fd752384c6830911d38be151921a5d152bb55e81fd752384c6830
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3bbc9cee50a4a4ca23bdc49f75ea8242d8a2193b3b
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < eff7cdf890b02596b8d73e910bdbdd489175dbdbeff7cdf890b02596b8d73e910bdbdd489175dbdb
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < 06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < 1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c01c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < a8799662fed1f8747edae87a1937549288baca6aa8799662fed1f8747edae87a1937549288baca6a
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < 6e5c8e8e024e147b834f56f2115aad241433679b6e5c8e8e024e147b834f56f2115aad241433679b
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < c516db6ab9eabbedbc430b4f93b0d8728e9b427fc516db6ab9eabbedbc430b4f93b0d8728e9b427f
linuxlinux>= 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 < eb85dace897c5986bc2f36b3c783c6abb8a4292eeb85dace897c5986bc2f36b3c783c6abb8a4292e
linuxlinux_kernel< 4.19.3164.19.316
linuxlinux_kernel>= 0 < 5.10.221-15.10.221-1

CVSS provenance

nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian5.3MEDIUM
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.