CVE-2024-26718: Vulnerability in linux-libc-dev package - Disable Tasklets
Summary
CVE-2024-26718: In the Linux kernel, the following vulnerability has been resolved: dm-crypt, dm-verity: disable tasklets Tasklets have an inherent problem with memory corruption. Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The linux-libc-dev package is a development package that provides the necessary header files and libraries for compiling C programs against the Linux kernel. It is an essential component for building and linking applications that interact with the kernel. The package is commonly used in Linux distributions, including Debian. However, the linux-libc-dev package is vulnerable to a specific issue related to tasklets.
Vulnerability Detail
The vulnerability (CVE-2024-26718) in the linux-libc-dev package affects the dm-crypt and dm-verity components. Tasklets, a mechanism used in the Linux kernel for deferred execution of code, have a flaw that can lead to memory corruption. The tasklet_action_common function calls tasklet_trylock, followed by the tasklet callback, and then tasklet_unlock. If the tasklet callback frees the structure containing the tasklet or calls code that may free it, tasklet_unlock will write into freed memory. This vulnerability can result in data corruption. Although attempts have been made to fix the issue for dm-crypt, the fix is not sufficient, and data corruption can still occur. Additionally, there is no fix available for dm-verity, which will write into freed memory with every tasklet-processed bio. Atomic workqueues, planned for kernel version 6.9, will address this memory corruption problem. However, an immediate solution is needed for stable kernels. As a temporary fix, this commit proposes disabling tasklets in both dm-crypt and dm-verity. The tasklet support is not removed, as it will be reused when atomic workqueues are implemented.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. Users are advised to follow the recommended fix provided by the package maintainers.
Conclusion
The linux-libc-dev package is vulnerable to a memory corruption issue related to tasklets in the dm-crypt and dm-verity components. While a complete fix is not available, a temporary solution has been proposed by disabling tasklets in both components. Users are advised to apply the necessary patches or updates provided by the package maintainers to mitigate the vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for linux →
FAQ
The linux-libc-dev package is a development package that provides the necessary header files and libraries for compiling C programs against the Linux kernel.
The vulnerability affects the dm-crypt and dm-verity components of the linux-libc-dev package.
The vulnerability can lead to memory corruption and data corruption in systems using the linux-libc-dev package.
No, there is currently no fix available for dm-verity. The proposed fix only addresses the issue in dm-crypt.
The memory corruption problem is planned to be addressed in kernel version 6.9 with the implementation of atomic workqueues.
Related vulnerabilities
Recent vulnerabilities recorded for linux.
