CVE-2024-37078

published 25 Jun 2024 · updated 5 Aug 2026

nilfs2: fix potential kernel bug due to lack of writeback flag waiting

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0ecfe3a92869a59668d27228dabbd7965e83567f, Kernel 1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d, Kernel 271dcd977ccda8c7a26e360425ae7b4db7d2ecc0 and 5 more.

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 <0f> 0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00 ... Call Trace: <TASK> 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 </TASK> 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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.30, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <0ecfe3a92869a59668d27228dabbd7965e83567f, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <271dcd977ccda8c7a26e360425ae7b4db7d2ecc0, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <33900d7eae616647e179eee1c66ebe654ee39627, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <614d397be0cf43412b3f94a0f6460eddced8ce92, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <95f6f81e50d858a7c9aa7c795ec14a0ac3819118, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <a4ca369ca221bb7e06c725792ac107f0e48e82e7, >=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <a75b8f493dfc48aa38c518430bd9e03b53bffebe0ecfe3a92869a59668d27228dabbd7965e83567f, 1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d, 271dcd977ccda8c7a26e360425ae7b4db7d2ecc0, 33900d7eae616647e179eee1c66ebe654ee39627, 614d397be0cf43412b3f94a0f6460eddced8ce92, 95f6f81e50d858a7c9aa7c795ec14a0ac3819118, a4ca369ca221bb7e06c725792ac107f0e48e82e7, a75b8f493dfc48aa38c518430bd9e03b53bffebe

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-37078 severity on Zeptric[![CVE-2024-37078](https://zeptric.io/badge/cve/CVE-2024-37078.svg)](https://zeptric.io/cve/CVE-2024-37078)