CVE-2024-43914
Last modified
CVE-2024-43914 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: md/raid5: avoid BUG_ON() while continue reshape after reassembling Currently, mdadm support --revert-reshape to abort the reshape while reassembling, as the test 07revert-grow. However, following BUG_ON() can be triggerred by the test: kernel BUG at drivers/md/raid5.c:6278! invalid opcode: 0000 [#1] PREEMPT SMP PTI irq event stamp: 158985 CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94 RIP: 0010:reshape_request+0x3f1/0xe60 Call Trace: <TASK> raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 </TASK> Root cause is that --revert-reshape update the raid_disks from 5 to 4, while reshape position is still set, and after reassembling the array, reshape position will be read from super block, then during reshape the checking of 'writepos' that is caculated by old reshape position will fail. Fix this panic the easy way first, by converting the BUG_ON() to WARN_ON(), and stop the reshape if checkings fail. Noted that mdadm must fix --revert-shape as well, and probably md/raid should enhance metadata validation as well, however this means reassemble will fail and there must be user tools to fix the wrong metadata.. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: md/raid5: avoid BUG_ON() while continue reshape after reassembling Currently, mdadm support --revert-reshape to abort the reshape while reassembling, as the test 07revert-grow. However, following BUG_ON() can be triggerred by the test: kernel BUG at drivers/md/raid5.c:6278! invalid opcode: 0000 [#1] PREEMPT SMP PTI irq event stamp: 158985 CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94 RIP: 0010:reshape_request+0x3f1/0xe60 Call Trace: <TASK> raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 </TASK> Root cause is that --revert-reshape update the raid_disks from 5 to 4, while reshape position is still set, and after reassembling the array, reshape position will be read from super block, then during reshape the checking of 'writepos' that is caculated by old reshape position will fail. Fix this panic the easy way first, by converting the BUG_ON() to WARN_ON(), and stop the reshape if checkings fail. Noted that mdadm must fix --revert-shape as well, and probably md/raid should enhance metadata validation as well, however this means reassemble will fail and there must be user tools to fix the wrong metadata.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 4.19.320 |
| Linux | Linux Kernel | >= 4.20, < 5.4.282 |
| Linux | Linux Kernel | >= 5.5, < 5.10.224 |
| Linux | Linux Kernel | >= 5.11, < 5.15.165 |
| Linux | Linux Kernel | >= 5.16, < 6.1.105 |
| Linux | Linux Kernel | >= 6.2, < 6.6.46 |
| Linux | Linux Kernel | >= 6.7, < 6.10.5 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-43914?
How severe is CVE-2024-43914?
How do I fix CVE-2024-43914?
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-43909In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4391The Happy Addons for Elementor plugin for WordPress is vulne…5.4
- CVE-2024-43910In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43911In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43912In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43913In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43915Improper Neutralization of Input During Web Page Generation …5.4
- CVE-2024-43916Authorization Bypass Through User-Controlled Key vulnerabili…7.1
- CVE-2024-43917Improper Neutralization of Special Elements used in an SQL C…9.8
- CVE-2024-43918Improper Neutralization of Special Elements used in an SQL C…9.8
- CVE-2024-43919Access Control vulnerability in YARPP YARPP allows . This i…9.8
- CVE-2024-4392The Jetpack – WP Security, Backup, Speed, & Growth plugin fo…5.4
Are you affected by CVE-2024-43914?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
