CVE-2024-26718 Details
Description
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/[email protected]/T/ [2] https://lore.kernel.org/lkml/[email protected]/
A vulnerability in the Linux kernel's tasklet handling within the dm-crypt and dm-verity components can lead to memory corruption. The issue arises because tasklet callbacks can free the structures containing the tasklets, causing subsequent tasklet operations to write into freed memory. While attempts were made to address this in dm-crypt, the fix was insufficient. As a result, dm-verity, which processes tasklets in a way that exacerbates the problem, remains vulnerable. This vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed by disabling tasklets in both dm-crypt and dm-verity. Users should upgrade to a patched version of the Linux kernel where this change has been implemented.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Sep 10, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.9, < 6.1.79 >= 6.2, < 6.6.18 >= 6.7, < 6.7.6 6.8 rc1 6.8 rc2 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 17, 2025 | Initial Analysis | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| Oct 22, 2024 | CVE Modified | kernel.org |
| May 29, 2024 | CVE Modified | kernel.org |
| May 14, 2024 | CVE Modified | kernel.org |
| Apr 3, 2024 | New CVE Received | kernel.org |