CVE-2024-26718dm-crypt, dm-verity: disable tasklets
- 7.8HighCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]/
Timeline
ID reserved
By Linux
- 44 days later
· 44 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 – < b825e0f9d68c178072bffd32dd34c39e3d2d597a
- affected 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 – < 30884a44e0cedc3dfda8c22432f3ba4078ec2d94
- affected 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 – < 5735a2671ffb70ea29ca83969fe01316ee2ed6fc
- affected 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 – < 0c45a20cbe68bc4d681734f5c03891124a274257
- affected 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 – < 0a9bab391e336489169b95cb0d4553d921302189
- affected 5.9
- unaffected < 5.9
- unaffected 5.15.169 – ≤ 5.15.*
- unaffected 6.1.79 – ≤ 6.1.*
- unaffected 6.6.18 – ≤ 6.6.*
- unaffected 6.7.6 – ≤ 6.7.*
- unaffected 6.8 – ≤ *
References
References5
- https://git.kernel.org/stable/c/b825e0f9d68c178072bffd32dd34c39e3d2d597a (opens in a new tab)
- https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-23980 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26718)Record last updated .