Vulnerability in Kernel: arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator
Summary
GSD-2022-1000503: arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator. Affects Kernel versions >= 1f80a5cf74a60997b92d2cde772edec093bec4d9, < 0a0a0be9ed6144ffb1698487d7c7bff3543cfe9c. 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 critical component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The vulnerability affects the arm64 architecture and specifically impacts the meson-sm1-odroid device tree source file. The issue arises from an incorrect enable-gpio pin being used for the tf-io regulator. This misconfiguration can lead to potential security vulnerabilities.
Vulnerability Detail
The vulnerability originates from a mistake in the meson-sm1-odroid device tree source file, where an incorrect enable-gpio pin is utilized for the tf-io regulator. This misconfiguration can result in security vulnerabilities that could potentially be exploited by attackers. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.16.10 by commit 0a0a0be9ed6144ffb1698487d7c7bff3543cfe9c. However, it was introduced in version v5.14 by commit 1f80a5cf74a60997b92d2cde772edec093bec4d9.
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 workaround, users can manually modify the meson-sm1-odroid device tree source file to use the correct enable-gpio pin for the tf-io regulator. The specific changes required can be found in the commit 0a0a0be9ed6144ffb1698487d7c7bff3543cfe9c. Here is an example of the modified code:
- enable-gpios = <&gpio GPIOX GPIO_ACTIVE_HIGH>;
+ enable-gpios = <&gpio GPIOY GPIO_ACTIVE_HIGH>;
Conclusion
In conclusion, the vulnerability in the Kernel's meson-sm1-odroid device tree source file can lead to potential security vulnerabilities. It is crucial to update the Linux Kernel to version v5.16.10 or later to mitigate this issue. Alternatively, users can apply the provided workaround by manually modifying the affected file. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, if exploited, it could potentially lead to security breaches and unauthorized access to the system.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and the tool will analyze it for any open-source vulnerabilities.
Yes, a workaround is available. You can manually modify the meson-sm1-odroid device tree source file to use the correct enable-gpio pin for the tf-io regulator. Please refer to the 'workaround' section for detailed instructions.
Yes, this vulnerability has been fixed in Linux Kernel version v5.16.10 by commit 0a0a0be9ed6144ffb1698487d7c7bff3543cfe9c.
You can find more information about this vulnerability in the official Linux Kernel repository. Please refer to the provided references link for detailed commit history and discussions.
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.
