Null Pointer Dereference in Linux Kernel's Pinmux Handling
Summary
CVE-2024-47141: In the Linux kernel, the following vulnerability has been resolved: pinmux: Use sequential access to access desc->pinmux data When two client of the same gpio call pinctrl_select_state() for the same functionality, we ar... 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 kernel is a core component of many operating systems, providing essential services for hardware management and system operations. It supports a wide range of functionalities, including process management, memory management, and device control. The kernel's pin multiplexing (pinmux) feature allows multiple functions to share the same GPIO pins, which is crucial for efficient hardware resource utilization. However, this feature is susceptible to vulnerabilities, particularly when multiple clients access shared resources simultaneously, leading to potential system crashes.
Vulnerability Detail
In the Linux kernel, a vulnerability has been identified in the pinmux handling mechanism. When two clients attempt to call the pinctrl_select_state() function for the same GPIO pin concurrently, a race condition can occur. This situation arises when one process updates the desc->mux_usecount without updating desc->mux_owner, while another process checks desc->mux_usecount and subsequently tries to access desc->mux_owner. If desc->mux_owner is NULL, this results in a null pointer dereference, causing a system crash. The vulnerability is critical as it can lead to denial of service, impacting system stability and reliability.
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
As a temporary workaround, you can serialize access to the pinmux settings by implementing a mutex lock around the pinctrl_select_state() function to prevent concurrent access. This can be done by modifying the function to include mutex locking mechanisms, ensuring that only one process can access the pinmux data at a time.
Conclusion
The CVE-2024-47141 vulnerability in the Linux kernel's pinmux handling poses a significant risk of system crashes due to null pointer dereferences. Users are strongly encouraged to update their systems to the latest patched versions to ensure stability and security. Implementing mutex locks can serve as a temporary measure until updates are applied.
See every vulnerability recorded for linux →
FAQ
CVE-2024-47141 is a vulnerability in the Linux kernel related to pinmux handling that can lead to a null pointer dereference and system crashes.
This vulnerability can cause denial of service by crashing the kernel when multiple processes attempt to access the same GPIO pin concurrently.
Yes, a patch is available in the updated versions of the Linux package. Users are advised to upgrade to the patched version to mitigate the risk.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
If immediate updates are not possible, implement a mutex lock around the pinctrl_select_state() function to prevent concurrent access as a temporary workaround.
Related vulnerabilities
Recent vulnerabilities recorded for linux.
