CVE-2024-40943

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix races between hole punching and AIO+DIO After commit "ocfs2: return real error code in ocfs2_dio_wr_get_block", fstests/generic/300 become from always failed to sometimes failed: ======================================================================== [ 473.293420 ] run fstests generic/300 [ 475.296983 ] JBD2: Ignoring recovery information on journal [ 475.302473 ] ocfs2: Mounting device (253,1) on (node local, slot 0) with ordered data mode. [ 494.290998 ] OCFS2: ERROR (device dm-1): ocfs2_change_extent_flag: Owner 5668 has an extent at cpos 78723 which can no longer be found [ 494.291609 ] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [ 494.292018 ] OCFS2: File system is now read-only. [ 494.292224 ] (kworker/19:11,2628,19):ocfs2_mark_extent_written:5272 ERROR: status = -30 [ 494.292602 ] (kworker/19:11,2628,19):ocfs2_dio_end_io_write:2374 ERROR: status = -3 fio: io_u error on file /mnt/scratch/racer: Read-only file system: write offset=460849152, buflen=131072 ========================================================================= In __blockdev_direct_IO, ocfs2_dio_wr_get_block is called to add unwritten extents to a list. extents are also inserted into extent tree in ocfs2_write_begin_nolock. Then another thread call fallocate to puch a hole at one of the unwritten extent. The extent at cpos was removed by ocfs2_remove_extent(). At end io worker thread, ocfs2_search_extent_list found there is no such extent at the cpos. T1 T2 T3 inode lock ... insert extents ... inode unlock ocfs2_fallocate __ocfs2_change_file_space inode lock lock ip_alloc_sem ocfs2_remove_inode_range inode ocfs2_remove_btree_range ocfs2_remove_extent ^---remove the extent at cpos 78723 ... unlock ip_alloc_sem inode unlock ocfs2_dio_end_io ocfs2_dio_end_io_write lock ip_alloc_sem ocfs2_mark_extent_written ocfs2_change_extent_flag ocfs2_search_extent_list ^---failed to find extent ... unlock ip_alloc_sem In most filesystems, fallocate is not compatible with racing with AIO+DIO, so fix it by adding to wait for all dio before fallocate/punch_hole like ext4.
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

17 Sep 2025, 15:02

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 4.7
References () https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e - () https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e - Patch
References () https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 - () https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 - Patch
References () https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 - () https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 - Patch
References () https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 - () https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 - Patch
References () https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 - () https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 - Patch
References () https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 - () https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 - Patch
References () https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f - () https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f - Patch
References () https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 - () https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 - Patch
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CWE CWE-362
First Time Linux
Linux linux Kernel

21 Nov 2024, 09:31

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e - () https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e -
References () https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 - () https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 -
References () https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 - () https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 -
References () https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 - () https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 -
References () https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 - () https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 -
References () https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 - () https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 -
References () https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f - () https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f -
References () https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 - () https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 -
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: ocfs2: corrige ejecuciones entre perforación y AIO+DIO Después de confirmar "ocfs2: devuelve código de error real en ocfs2_dio_wr_get_block", fstests/generic/300 pasa de siempre falló a a veces falló: = ==================================================== ===================== [ 473.293420 ] ejecute fstests generic/300 [ 475.296983 ] JBD2: ignorando la información de recuperación en el diario [ 475.302473 ] ocfs2: Dispositivo de montaje (253,1 ) en (nodo local, ranura 0) con modo de datos ordenados. [ 494.290998 ] OCFS2: ERROR (dispositivo dm-1): ocfs2_change_extent_flag: El propietario 5668 tiene una extensión en cpos 78723 que ya no se puede encontrar [ 494.291609 ] Se descubrió corrupción en el disco. Ejecute fsck.ocfs2 una vez que el sistema de archivos esté desmontado. [ 494.292018 ] OCFS2: el sistema de archivos ahora es de solo lectura. [ 494.292224 ] (kworker/19:11,2628,19):ocfs2_mark_extent_write:5272 ERROR: estado = -30 [ 494.292602 ] (kworker/19:11,2628,19):ocfs2_dio_end_io_write:2374 ERROR: estado = -3 fio: Error io_u en el archivo /mnt/scratch/racer: sistema de archivos de solo lectura: escritura offset=460849152, buflen=131072 ========================== ================================================= En __blockdev_direct_IO , se llama a ocfs2_dio_wr_get_block para agregar extensiones no escritas a una lista. Las extensiones también se insertan en el árbol de extensiones en ocfs2_write_begin_nolock. Luego, otro hilo llama a fallocate para hacer un agujero en una de las extensiones no escritas. La extensión en cpos fue eliminada por ocfs2_remove_extent(). Al final del hilo de trabajo de io, ocfs2_search_extent_list descubrió que no existe tal extensión en los cpos. T1 T2 T3 bloqueo de inodo... insertar extensiones... desbloqueo de inodo ocfs2_fallocate __ocfs2_change_file_space bloqueo de inodo bloqueo ip_alloc_sem ocfs2_remove_inode_range inodo ocfs2_remove_btree_range ocfs2_remove_extent ^---eliminar la extensión en cpos 78723... desbloquear inodo ip_alloc_sem desbloquear ocfs2_dio_end_io ocfs2_dio_end_io_write bloquear ip_alloc_sem ocfs2_mark_extent_writing ocfs2_change_extent_flag ocfs2_search_extent_list ^ ---no se pudo encontrar la extensión... desbloquear ip_alloc_sem En la mayoría de los sistemas de archivos, fallocate no es compatible con ejecuciones con AIO+DIO, así que solucionelo agregando esperar a que todos los dio antes de fallocate/punch_hole como ext4.

12 Jul 2024, 16:34

Type Values Removed Values Added
New CVE

Information

Published : 2024-07-12 13:15

Updated : 2025-09-17 15:02


NVD link : CVE-2024-40943

Mitre link : CVE-2024-40943

CVE.ORG link : CVE-2024-40943


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-362

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')