CVE-2024-57929

In the Linux kernel, the following vulnerability has been resolved: dm array: fix releasing a faulty array block twice in dm_array_cursor_end When dm_bm_read_lock() fails due to locking or checksum errors, it releases the faulty block implicitly while leaving an invalid output pointer behind. The caller of dm_bm_read_lock() should not operate on this invalid dm_block pointer, or it will lead to undefined result. For example, the dm_array_cursor incorrectly caches the invalid pointer on reading a faulty array block, causing a double release in dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put(). Reproduce steps: 1. initialize a cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. wipe the second array block offline dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2>/dev/null | hexdump -e '1/8 "%u\n"') ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2>/dev/null | hexdump -e '1/8 "%u\n"') dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock 3. try reopen the cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" Kernel logs: (snip) device-mapper: array: array_block_check failed: blocknr 0 != wanted 10 device-mapper: block manager: array validator check failed for block 10 device-mapper: array: get_ablock failed device-mapper: cache metadata: dm_array_cursor_next for mapping failed ------------[ cut here ]------------ kernel BUG at drivers/md/dm-bufio.c:638! Fix by setting the cached block pointer to NULL on errors. In addition to the reproducer described above, this fix can be verified using the "array_cursor/damaged" test in dm-unit: dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>
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:6.13:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*

History

26 Sep 2025, 19:09

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 7.1
References () https://git.kernel.org/stable/c/017c4470bff53585370028fec9341247bad358ff - () https://git.kernel.org/stable/c/017c4470bff53585370028fec9341247bad358ff - Patch
References () https://git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da - () https://git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da - Patch
References () https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46 - () https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46 - Patch
References () https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b - () https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b - Patch
References () https://git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979 - () https://git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979 - Patch
References () https://git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8 - () https://git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8 - Patch
References () https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7 - () https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7 - Patch
CWE CWE-672
CPE cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
First Time Linux
Linux linux Kernel

02 Feb 2025, 11:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b -
  • () https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7 -

23 Jan 2025, 17:15

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dm array: se corrige la liberación de un bloque de matriz defectuoso dos veces en dm_array_cursor_end Cuando dm_bm_read_lock() falla debido a errores de bloqueo o suma de comprobación, libera el bloque defectuoso implícitamente mientras deja atrás un puntero de salida no válido. El llamador de dm_bm_read_lock() no debe operar en este puntero dm_block no válido, o conducirá a un resultado indefinido. Por ejemplo, dm_array_cursor almacena en caché incorrectamente el puntero no válido al leer un bloque de matriz defectuoso, lo que causa una doble liberación en dm_array_cursor_end(), y luego alcanza el BUG_ON en dm-bufio cache_put(). Reproducir los pasos: 1. inicializar un dispositivo de caché dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. borrar el segundo bloque de matriz sin conexión dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2&gt;/dev/null | hexdump -e '1/8 "%u\n"') ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2&gt;/dev/null | hexdump -e '1/8 "%u\n"') dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock 3. Intente volver a abrir el dispositivo de caché dmsetup create cmeta --table "0 8192 lineal /dev/sdc 0" dmsetup create cdata --table "0 65536 lineal /dev/sdc 8192" dmsetup create corig --table "0 524288 lineal /dev/sdc $262144" dmsetup create cache --table "0 524288 caché /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" Registros del kernel: (snip) device-mapper: array: array_block_check failed: blocknr 0 != wanted 10 device-mapper: block manager: array validator check failed for block 10 device-mapper: array: get_ablock failed device-mapper: cache metadata: dm_array_cursor_next for mapping failed ------------[ corte aquí ]------------ ¡ERROR del kernel en drivers/md/dm-bufio.c:638! Se corrige configurando el puntero de bloque en caché en NULL en caso de errores. Además del reproductor descrito anteriormente, esta corrección se puede verificar utilizando la prueba "array_cursor/damaged" en dm-unit: dm-unit run /pdata/array_cursor/damaged --kernel-dir
References
  • () https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46 -

19 Jan 2025, 12:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-01-19 12:15

Updated : 2025-09-26 19:09


NVD link : CVE-2024-57929

Mitre link : CVE-2024-57929

CVE.ORG link : CVE-2024-57929


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-672

Operation on a Resource after Expiration or Release