CVE-2024-26718

Advisory lineage Upstream: 0 Downstream: 24
Analyzed
Published: 03 Apr 2024, 14:55
Last modified:11 May 2026, 20:02

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

03 Apr 2024, 14:55
Published
Vulnerability first disclosed
11 May 2026, 20:02
Last Modified
Vulnerability information updated

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/d390d7ee-f142-44d3-822a-87949e14608b@suse.de/T/ [2] https://lore.kernel.org/lkml/20240130091300.2968534-1-tj@kernel.org/

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 5%

Techniques & Countermeasures

  • CWE-787•Out-of-bounds Write

    The product writes data past the end, or before the beginning, of the intended buffer.

Affected Systems

  • linux•linux

    ≥ 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, < b825e0f9d68c178072bffd32dd34c39e3d2d597a | ≥ 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, < 30884a44e0cedc3dfda8c22432f3ba4078ec2d94 | ≥ 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, < 5735a2671ffb70ea29ca83969fe01316ee2ed6fc | ≥ 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, < 0c45a20cbe68bc4d681734f5c03891124a274257 | ≥ 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, < 0a9bab391e336489169b95cb0d4553d921302189 | 5.9

  • linux•linux_kernel

    ≥ 5.9, < 6.1.79 | ≥ 6.2, < 6.6.18 | ≥ 6.7, < 6.7.6 | 6.8:rc1 | 6.8:rc2

References (5)