cbcvebase.
CVE-2024-26696
published 2024-04-03

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

PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
9.0th percentile
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause is that the wait for writeback completion in nilfs_page_mkwrite() is conditional, and if the backing device does not require stable writes, data may be modified without waiting. Fix these issues by making nilfs_page_mkwrite() wait for writeback to finish regardless of the stable write requirement of the backing device.

Affected

25 ranges
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.82-1 (bookworm)linux 6.1.82-1 (bookworm)
linuxlinux
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 228742b2ddfb99dfd71e5a307e6088ab6836272e228742b2ddfb99dfd71e5a307e6088ab6836272e
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 862ee4422c38be5c249844a684b00d0dbe9d1e46862ee4422c38be5c249844a684b00d0dbe9d1e46
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 98a4026b22ff440c7f47056481bcbbe442f607d698a4026b22ff440c7f47056481bcbbe442f607d6
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 7e9b622bd0748cc104d66535b76d9b3535f9dc0f7e9b622bd0748cc104d66535b76d9b3535f9dc0f
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 8494ba2c9ea00a54d5b50e69b22c55a8958bce328494ba2c9ea00a54d5b50e69b22c55a8958bce32
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < ea5ddbc11613b55e5128c85f57b08f907abd9b28ea5ddbc11613b55e5128c85f57b08f907abd9b28
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < e38585401d464578d30f5868ff4ca54475c34f7de38585401d464578d30f5868ff4ca54475c34f7d
linuxlinux>= 1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 < 38296afe3c6ee07319e01bb249aa4bb47c07b53438296afe3c6ee07319e01bb249aa4bb47c07b534
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.216-15.10.216-1
linuxlinux_kernel>= 0 < 6.1.82-16.1.82-1
linuxlinux_kernel>= 0 < 6.7.7-16.7.7-1
linuxlinux_kernel>= 0 < 6.7.7-16.7.7-1
linuxlinux_kernel>= 0 < 5.4.0-181.2015.4.0-181.201
linuxlinux_kernel>= 0 < 5.15.0-106.1165.15.0-106.116
linuxlinux_kernel>= 3.9 < 4.19.3074.19.307
linuxlinux_kernel>= 4.20 < 5.4.2695.4.269
linuxlinux_kernel>= 5.11 < 5.15.1495.15.149
linuxlinux_kernel>= 5.16 < 6.1.796.1.79
linuxlinux_kernel>= 5.5 < 5.10.2105.10.210
linuxlinux_kernel>= 6.2 < 6.6.186.6.18
linuxlinux_kernel>= 6.7 < 6.7.66.7.6

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.0HIGH
vendor_ubuntu7.0HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
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.