cbcvebase.
CVE-2024-37078
published 2024-06-25

CVE-2024-37078: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential kernel bug due to lack of writeback flag waiting Destructive writes…

PriorityP429high7.1CVSS 3.1
AVLACLPRLUINSUCNIHAH
EPSS
0.25%
16.5th percentile
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential kernel bug due to lack of writeback flag waiting Destructive writes to a block device on which nilfs2 is mounted can cause a kernel bug in the folio/page writeback start routine or writeback end routine (__folio_start_writeback in the log below): kernel BUG at mm/page-writeback.c:3070! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI ... RIP: 0010:__folio_start_writeback+0xbaa/0x10e0 Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00 ... Call Trace: nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2] nilfs_segctor_construct+0x181/0x6b0 [nilfs2] nilfs_segctor_thread+0x548/0x11c0 [nilfs2] kthread+0x2f0/0x390 ret_from_fork+0x4b/0x80 ret_from_fork_asm+0x1a/0x30 This is because when the log writer starts a writeback for segment summary blocks or a super root block that use the backing device's page cache, it does not wait for the ongoing folio/page writeback, resulting in an inconsistent writeback state. Fix this issue by waiting for ongoing writebacks when putting folios/pages on the backing device into writeback state.

Affected

27 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.99-1 (bookworm)linux 6.1.99-1 (bookworm)
debianlinux-6.1< linux 6.1.99-1 (bookworm)linux 6.1.99-1 (bookworm)
linuxlinux
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 95f6f81e50d858a7c9aa7c795ec14a0ac381911895f6f81e50d858a7c9aa7c795ec14a0ac3819118
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < a75b8f493dfc48aa38c518430bd9e03b53bffebea75b8f493dfc48aa38c518430bd9e03b53bffebe
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 0ecfe3a92869a59668d27228dabbd7965e83567f0ecfe3a92869a59668d27228dabbd7965e83567f
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 33900d7eae616647e179eee1c66ebe654ee3962733900d7eae616647e179eee1c66ebe654ee39627
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 271dcd977ccda8c7a26e360425ae7b4db7d2ecc0271dcd977ccda8c7a26e360425ae7b4db7d2ecc0
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 614d397be0cf43412b3f94a0f6460eddced8ce92614d397be0cf43412b3f94a0f6460eddced8ce92
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < 1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d
linuxlinux>= 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 < a4ca369ca221bb7e06c725792ac107f0e48e82e7a4ca369ca221bb7e06c725792ac107f0e48e82e7
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.221-15.10.221-1
linuxlinux_kernel>= 0 < 6.1.99-16.1.99-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 5.4.0-195.2155.4.0-195.215
linuxlinux_kernel>= 0 < 5.15.0-121.1315.15.0-121.131
linuxlinux_kernel>= 0 < 6.8.0-44.446.8.0-44.44
linuxlinux_kernel>= 2.6.30 < 4.19.3174.19.317
linuxlinux_kernel>= 4.20 < 5.4.2795.4.279
linuxlinux_kernel>= 5.11 < 5.15.1625.15.162
linuxlinux_kernel>= 5.16 < 6.1.956.1.95
linuxlinux_kernel>= 5.5 < 5.10.2215.10.221

CVSS provenance

nvdv3.17.1HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian7.1HIGH
vendor_redhat7.1HIGH
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.