CWE
787
Advisory Published
CVE Published
Updated

CVE-2024-26718: dm-crypt, dm-verity: disable tasklets

First published: Wed Apr 03 2024(Updated: )

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/

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.9<6.1.79
Linux Kernel>=6.2<6.6.18
Linux Kernel>=6.7<6.7.6
Linux Kernel=6.8-rc1
Linux Kernel=6.8-rc2
debian/linux<=5.10.223-1<=5.10.234-1
6.1.129-1
6.1.128-1
6.12.21-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-26718?

    CVE-2024-26718 has been categorized as a high severity vulnerability due to potential memory corruption issues in the Linux kernel.

  • How do I fix CVE-2024-26718?

    To fix CVE-2024-26718, users should update their Linux kernel to versions 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1 if they are currently running affected versions.

  • Which Linux kernel versions are affected by CVE-2024-26718?

    CVE-2024-26718 affects Linux kernel versions up to and including 5.10.226-1.

  • What impact does CVE-2024-26718 have on Linux security?

    CVE-2024-26718 may allow attackers to exploit memory corruption vulnerabilities, potentially leading to privilege escalation or system crashes.

  • Is CVE-2024-26718 specific to any Linux distribution?

    While CVE-2024-26718 is a vulnerability found in the Linux kernel, it specifically impacts systems running Debian-based distributions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203