CVE-2024-43914

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. 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 --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.

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 Patch
https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 Patch
https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 Patch
https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab Patch
https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 Patch
https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 Patch
https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 Patch
https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

05 Sep 2024, 18:03

Type Values Removed Values Added
CWE NVD-CWE-noinfo
References () https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 - () https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 - Patch
References () https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 - () https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 - Patch
References () https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 - () https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 - Patch
References () https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab - () https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab - Patch
References () https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 - () https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 - Patch
References () https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 - () https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 - Patch
References () https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 - () https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 - Patch
References () https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 - () https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 - Patch
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
First Time Linux linux Kernel
Linux
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: md/raid5: evite BUG_ON() mientras continúa la remodelación después del reensamblaje. Actualmente, mdadm admite --revert-reshape para cancelar la remodelación mientras se reensambla, como muestra la prueba 07revert-grow. Sin embargo, la prueba puede activar el siguiente BUG_ON(): kernel ERROR en drivers/md/raid5.c:6278! código de operación no válido: 0000 [#1] PREEMPT SMP PTI sello de evento irq: 158985 CPU: 6 PID: 891 Comm: md0_reshape No contaminado 6.9.0-03335-g7592a0b0049a #94 RIP: 0010:reshape_request+0x3f1/0xe60 Seguimiento de llamadas: 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 La causa principal es que --revert-resha pe actualizar los raid_disks de 5 a 4, mientras la posición de remodelación aún está establecida, y después de volver a ensamblar la matriz, la posición de remodelación se leerá desde el superbloque, luego, durante la remodelación, fallará la verificación de 'writepos' calculada por la posición de remodelación anterior. Primero solucione este pánico de la manera más fácil, convirtiendo BUG_ON() en WARN_ON() y detenga la remodelación si las comprobaciones fallan. Se señaló que mdadm también debe corregir --revert-shape, y probablemente md/raid también debería mejorar la validación de metadatos; sin embargo, esto significa que el reensamblaje fallará y debe haber herramientas de usuario para corregir los metadatos incorrectos.

26 Aug 2024, 11:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-08-26 11:15

Updated : 2024-09-05 18:03

NVD link : CVE-2024-43914

Mitre link : CVE-2024-43914

CVE.ORG link : CVE-2024-43914

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo