CVE-2024-43914
"Linux Kernel md RAID5 BUG() to WARN() Vulnerability in mga"
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.
INFO
Published Date :
Aug. 26, 2024, 11:15 a.m.
Last Modified :
Sept. 5, 2024, 6:03 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-43914.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-43914 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-43914 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Sep. 05, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 No Types Assigned https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 Patch Changed Reference Type https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 No Types Assigned https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 Patch Changed Reference Type https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 No Types Assigned https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 Patch Changed Reference Type https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab No Types Assigned https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab Patch Changed Reference Type https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 No Types Assigned https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 Patch Changed Reference Type https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 No Types Assigned https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 Patch Changed Reference Type https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 No Types Assigned https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 Patch Changed Reference Type https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 No Types Assigned https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 Patch Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.320 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.282 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.224 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.165 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.105 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.46 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.5 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 26, 2024
Action Type Old Value New Value Added 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. Added Reference kernel.org https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-43914 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-43914
weaknesses.