Vulnerability · Published Jun 25, 2024 · Assigned by Linux
CVE-2024-37078nilfs2: fix potential kernel bug due to lack of writeback flag waiting
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.99-1 | DEBIAN-CVE-2024-37078 |
| Debian:12 | linux | 6.1.99-1 | DSA-5731-1 |
| Debian:13 | linux | 6.9.7-1 | DEBIAN-CVE-2024-37078 |
| Debian:14 | linux | 6.9.7-1 | DEBIAN-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux | 5.15.0-121.131 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux | 5.15.0-121.131 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux | 6.8.0-44.44 | USN-6999-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-44.44 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1069.75 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1069.75 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1015.16 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1015.16 | USN-6999-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1015.16~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1072.81 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1072.81 | USN-7009-1 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1014.16 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1014.16 | USN-7004-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1014.16~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1072.81.1 | USN-7009-1 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1072.81.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1068.76 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1068.76 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1014.16 | USN-6999-1 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1014.16 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1014.16~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1066.72 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1066.72 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1010.13 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1010.13 | USN-6999-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1052.59 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1052.59 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-45.45~22.04.1 | USN-7029-1 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-45.45~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1062.65 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1062.65 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1012.12 | USN-6999-1 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1012.12 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1012.12~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1064.70 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1064.70 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1066.71 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1066.71 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-121.131 | USN-7007-3 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-121.131 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-44.44.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-44.44.1 | USN-6999-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-44.44.1~22.04.1 | USN-7008-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-44.44.1~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1064.65 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1064.65 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1013.14 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1013.14 | USN-7005-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1013.14~22.04.1 | USN-7005-2 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1013.14~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1013.14.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1013.14.1 | USN-7005-1 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1028.28 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1016.16 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1012.12 | USN-6999-1 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1012.12 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1067.73 | USN-7007-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1067.73 | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1012.12 | USN-6999-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1012.12 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1012.12~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1062.65 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1062.65 | USN-7007-1 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1011.12 | USN-6999-2 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1011.12 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-44.44.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-44.44.1~22.04.1 | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-37078 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1035.39 | UBUNTU-CVE-2024-37078 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 95f6f81e50d858a7c9aa7c795ec14a0ac38191189ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before a75b8f493dfc48aa38c518430bd9e03b53bffebe9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 0ecfe3a92869a59668d27228dabbd7965e83567f9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 33900d7eae616647e179eee1c66ebe654ee396279ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 271dcd977ccda8c7a26e360425ae7b4db7d2ecc09ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 614d397be0cf43412b3f94a0f6460eddced8ce929ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before 1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – before a4ca369ca221bb7e06c725792ac107f0e48e82e7 |
| Linux | Linux | 2.6.30 |
References
- https://git.kernel.org/stable/c/95f6f81e50d858a7c9aa7c795ec14a0ac3819118
- https://git.kernel.org/stable/c/a75b8f493dfc48aa38c518430bd9e03b53bffebe
- https://git.kernel.org/stable/c/0ecfe3a92869a59668d27228dabbd7965e83567f
- https://git.kernel.org/stable/c/33900d7eae616647e179eee1c66ebe654ee39627
- https://git.kernel.org/stable/c/271dcd977ccda8c7a26e360425ae7b4db7d2ecc0
- https://git.kernel.org/stable/c/614d397be0cf43412b3f94a0f6460eddced8ce92
- https://git.kernel.org/stable/c/1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d
- https://git.kernel.org/stable/c/a4ca369ca221bb7e06c725792ac107f0e48e82e7
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html