CVE-2024-26718

In the Linux kernel, the following vulnerability has been resolved: dm-crypt, dm-verity: disable tasklets Tasklets have an inherent problem with memory corruption. The function tasklet_action_common calls tasklet_trylock, then it calls the tasklet callback and then it calls tasklet_unlock. If the tasklet callback frees the structure that contains the tasklet or if it calls some code that may free it, tasklet_unlock will write into free memory. The commits 8e14f610159d and d9a02e016aaf try to fix it for dm-crypt, but it is not a sufficient fix and the data corruption can still happen [1]. There is no fix for dm-verity and dm-verity will write into free memory with every tasklet-processed bio. There will be atomic workqueues implemented in the kernel 6.9 [2]. They will have better interface and they will not suffer from the memory corruption problem. But we need something that stops the memory corruption now and that can be backported to the stable kernels. So, I'm proposing this commit that disables tasklets in both dm-crypt and dm-verity. This commit doesn't remove the tasklet support, because the tasklet code will be reused when atomic workqueues will be implemented. [1] https://lore.kernel.org/all/d390d7ee-f142-44d3-822a-87949e14608b@suse.de/T/ [2] https://lore.kernel.org/lkml/20240130091300.2968534-1-tj@kernel.org/
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:6.8:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*

History

17 Mar 2025, 16:01

Type Values Removed Values Added
CWE CWE-787
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189 - () https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189 - Patch
References () https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 - () https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 - Patch
References () https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 - () https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 - Patch
References () https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc - () https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc - Patch
References () https://git.kernel.org/stable/c/b825e0f9d68c178072bffd32dd34c39e3d2d597a - () https://git.kernel.org/stable/c/b825e0f9d68c178072bffd32dd34c39e3d2d597a - Patch
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5

21 Nov 2024, 09:02

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189 - () https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189 -
References () https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 - () https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 -
References () https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 - () https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 -
References () https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc - () https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc -

22 Oct 2024, 15:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/b825e0f9d68c178072bffd32dd34c39e3d2d597a -
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dm-crypt, dm-verity: deshabilitar tasklets Los tasklets tienen un problema inherente con la corrupción de la memoria. La función tasklet_action_common llama a tasklet_trylock, luego llama a la devolución de llamada del tasklet y luego llama a tasklet_unlock. Si la devolución de llamada del tasklet libera la estructura que contiene el tasklet o si llama a algún código que pueda liberarlo, tasklet_unlock escribirá en la memoria libre. Las confirmaciones 8e14f610159d y d9a02e016aaf intentan solucionarlo para dm-crypt, pero no es una solución suficiente y la corrupción de datos aún puede ocurrir [1]. No hay ninguna solución para dm-verity y dm-verity escribirá en la memoria libre con cada biografía procesada por tasklet. Habrá colas de trabajo atómicas implementadas en el kernel 6.9 [2]. Tendrán una mejor interfaz y no sufrirán el problema de corrupción de memoria. Pero necesitamos algo que detenga la corrupción de la memoria ahora y que pueda ser compatible con los núcleos estables. Entonces, propongo esta confirmación que deshabilita los tasklets tanto en dm-crypt como en dm-verity. Esta confirmación no elimina la compatibilidad con el tasklet, porque el código del tasklet se reutilizará cuando se implementen las colas de trabajo atómicas. [1] https://lore.kernel.org/all/d390d7ee-f142-44d3-822a-87949e14608b@suse.de/T/ [2] https://lore.kernel.org/lkml/20240130091300.2968534-1- tj@kernel.org/

03 Apr 2024, 15:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-04-03 15:15

Updated : 2025-03-17 16:01


NVD link : CVE-2024-26718

Mitre link : CVE-2024-26718

CVE.ORG link : CVE-2024-26718


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-787

Out-of-bounds Write