pinctrl: single: fix potential NULL dereference in Kernel
Summary
GSD-2023-1002405: pinctrl: single: fix potential NULL dereference. Affects Kernel versions >= 571aec4df5b72a80f80d1e524da8fbd7ff525c98, < 2b763f7de108cb1a5ad5ed08e617d677341947cb. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a crucial component of the Linux operating system that manages the communication between hardware and software. It provides essential services and functions, including device drivers, memory management, and process scheduling. The pinctrl subsystem in the Kernel is responsible for managing pin control and configuration for various hardware devices. This vulnerability affects the pinctrl single driver in the Kernel.
Vulnerability Detail
The pinctrl single driver in the Kernel is susceptible to a potential NULL dereference issue. This vulnerability could be exploited by an attacker to cause a denial-of-service condition or potentially execute arbitrary code. The vulnerability was introduced in version v4.11 of the Kernel and was fixed in version v5.4.232. The specific commit that addressed this issue is 2b763f7de108cb1a5ad5ed08e617d677341947cb.
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 →
Conclusion
The pinctrl single driver in the Kernel is vulnerable to a potential NULL dereference issue. To mitigate this vulnerability, it is crucial to update the Kernel to version v5.4.232 or later. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could lead to a denial-of-service condition or potential code execution.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there are no known exploits for this vulnerability.
No specific workaround has been provided for this vulnerability. It is recommended to update the Kernel to the fixed version.
You can find more information about this vulnerability in the official Linux Kernel repository and the associated commit 2b763f7de108cb1a5ad5ed08e617d677341947cb.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
