Answer in brief
CVE-2024-26718 records a High severity (CVSS 7.8) vulnerability in dm-crypt, dm-verity: disable tasklets. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 <b825e0f9d68c178072bffd32dd34c39e3d2d597a || >=39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 <30884a44e0cedc3dfda8c22432f3ba4078ec2d94 || >=39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 <5735a2671ffb70ea29ca83969fe01316ee2ed6fc || >=39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 <0c45a20cbe68bc4d681734f5c03891124a274257 || >=39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 <0a9bab391e336489169b95cb0d4553d921302189 | b825e0f9d68c178072bffd32dd34c39e3d2d597a, 30884a44e0cedc3dfda8c22432f3ba4078ec2d94, 5735a2671ffb70ea29ca83969fe01316ee2ed6fc, 0c45a20cbe68bc4d681734f5c03891124a274257, 0a9bab391e336489169b95cb0d4553d921302189 |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
Apr 3, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]/
Quoted source text, attributed separately from HOL analysis.