cbcvebase.
CVE-2024-43914
published 2024-08-26

CVE-2024-43914: In the Linux kernel, the following vulnerability has been resolved: md/raid5: avoid BUG_ON() while continue reshape after reassembling Currently, mdadm support…

PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.5th percentile
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: 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 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.

Affected

31 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.106-1 (bookworm)linux 6.1.106-1 (bookworm)
debianlinux-6.1< linux 6.1.106-1 (bookworm)linux 6.1.106-1 (bookworm)
linuxlinux
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 2c92f8c1c456d556f15cbf51667b385026b2e6a02c92f8c1c456d556f15cbf51667b385026b2e6a0
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 6b33c468d543f6a83de2d61f09fec74b27e19fd26b33c468d543f6a83de2d61f09fec74b27e19fd2
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < c384dd4f1fb3b14a2fd199360701cc163ea88705c384dd4f1fb3b14a2fd199360701cc163ea88705
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < bf0ff69a42a3d2d46876d0514ecf13dffc516666bf0ff69a42a3d2d46876d0514ecf13dffc516666
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 3b33740c1750a39e046339ff9240e954f01567073b33740c1750a39e046339ff9240e954f0156707
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 775a9ba16c9ffe98fe54ebf14e55d5660f2bf600775a9ba16c9ffe98fe54ebf14e55d5660f2bf600
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 4811d6e5d9f4090c3e0ff9890eb24077108046ab4811d6e5d9f4090c3e0ff9890eb24077108046ab
linuxlinux>= ec32a2bd35bd6b933a5db6542c48210ce069a376 < 305a5170dc5cf3d395bb4c4e9239bca6d0b54b49305a5170dc5cf3d395bb4c4e9239bca6d0b54b49
linuxlinux_kernel< 4.19.3204.19.320
linuxlinux_kernel>= 0 < 5.10.226-15.10.226-1
linuxlinux_kernel>= 0 < 6.1.106-16.1.106-1
linuxlinux_kernel>= 0 < 6.10.6-16.10.6-1
linuxlinux_kernel>= 0 < 6.10.6-16.10.6-1
linuxlinux_kernel>= 0 < 5.4.0-200.2205.4.0-200.220
linuxlinux_kernel>= 0 < 5.15.0-125.1355.15.0-125.135
linuxlinux_kernel>= 0 < 6.8.0-50.516.8.0-50.51
linuxlinux_kernel>= 0 < 4.4.0-263.2974.4.0-263.297
linuxlinux_kernel>= 0 < 4.15.0-233.2454.15.0-233.245
linuxlinux_kernel>= 4.20 < 5.4.2825.4.282
linuxlinux_kernel>= 5.11 < 5.15.1655.15.165
linuxlinux_kernel>= 5.16 < 6.1.1056.1.105
linuxlinux_kernel>= 5.5 < 5.10.2245.10.224

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.