CVE-2024-37078
Last modified
CVE-2024-37078 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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.. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.30, < 4.19.317 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.279 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.221 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.162 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.95 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.35 | — |
| Linux | Linux Kernel | >= 6.7, < 6.9.5 | — |
| Linux | Linux Kernel | 6.10 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-37078?
How severe is CVE-2024-37078?
How do I fix CVE-2024-37078?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-37066A command injection vulnerability exists in Wyze V4 Pro firm…8.8
- CVE-2024-37068IBM Maximo Application Suite - Manage Component 8.10, 8.11, …7.5
- CVE-2024-3707Information exposure vulnerability in OpenGnsys affecting ve…5.3
- CVE-2024-37070IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could …6.5
- CVE-2024-37071IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Se…6.5
- CVE-2024-37077in OpenHarmony v4.0.0 and prior versions allow a remote atta…9.8
- CVE-2024-37079vCenter Server contains a heap-overflow vulnerability in the…9.8
- CVE-2024-3708Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-37080vCenter Server contains a heap-overflow vulnerability in the…9.8
- CVE-2024-37081The vCenter Server contains multiple local privilege escalat…7.8
- CVE-2024-37082When deploying Cloud Foundry together with the haproxy-boshr…9.1
- CVE-2024-37084In Spring Cloud Data Flow versions prior to 2.11.4, a malic…8.8
Are you affected by CVE-2024-37078?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
