CVE-2024-26756: Vulnerability in linux-libc-dev package - kernel: md: Don't register sync_thread for reshape directly
Summary
CVE-2024-26756: In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is interrupted, then reassemble the array will register sync_thread directly f... 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 programs that use the Linux kernel's C library interface. It is an essential component for building and running applications on Linux systems. This vulnerability affects version 6.1.90-1 of the linux-libc-dev package.
Vulnerability Detail
The vulnerability in the linux-libc-dev package arises from a flaw in the Linux kernel. Specifically, when a reshape operation is interrupted, the array reassembly process registers the sync_thread directly from pers->run(). However, there is no guarantee that md_do_sync() will be executed, leading to a hang in stop_sync_thread() because the 'MD_RECOVERY_RUNNING' flag cannot be cleared. This vulnerability can be triggered by certain test scenarios and can result in a denial-of-service condition. The issue has been addressed by removing the code to register sync_thread directly from raid10 and raid5, and instead, md_check_recovery() is responsible for registering sync_thread.
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 known workaround for this vulnerability. It is advised to apply the fix by updating the linux-libc-dev package as mentioned above.
Conclusion
In conclusion, the linux-libc-dev package is vulnerable to a flaw in the Linux kernel that can lead to a denial-of-service condition. It is crucial to update the package to the latest version that includes the fix to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for linux →
FAQ
The linux-libc-dev package provides the necessary header files and libraries for compiling programs that use the Linux kernel's C library interface. It is an essential component for building and running applications on Linux systems.
This vulnerability can lead to a denial-of-service condition in certain scenarios. An attacker can exploit this flaw to disrupt the normal operation of the affected system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes your manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.
No, there are no known workarounds for this vulnerability. It is recommended to update the linux-libc-dev package to the latest version that includes the fix.
You can find more information about this vulnerability in the official CVE report (https://nvd.nist.gov/vuln/detail/CVE-2024-26756) and the Debian Security Tracker (https://salsa.debian.org/security-tracker-team/security-tracker).
Related vulnerabilities
Recent vulnerabilities recorded for linux.
