https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 00:14:04 +0000 https://vulnerability.circl.lu/vuln/cve-2024-26718 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt, dm-verity: disable tasklets</p> <p>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.</p> <p>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.</p> <p>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.</p> <p>But we need something that stops the memory corruption now and that can be backported to the stable kernels. So, I&#39;m proposing this commit that disables tasklets in both dm-crypt and dm-verity. This commit doesn&#39;t remove the tasklet support, because the tasklet code will be reused when atomic workqueues will be implemented.</p> <p>[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/</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-crypt, dm-verity: disable tasklets</p> <p>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.</p> <p>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.</p> <p>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.</p> <p>But we need something that stops the memory corruption now and that can be backported to the stable kernels. So, I&#39;m proposing this commit that disables tasklets in both dm-crypt and dm-verity. This commit doesn&#39;t remove the tasklet support, because the tasklet code will be reused when atomic workqueues will be implemented.</p> <p>[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/</p> https://vulnerability.circl.lu/vuln/cve-2024-26718