Vulnerability in Kernel: regulator: rt4801
Summary
GSD-2021-1000994: regulator: rt4801: Fix NULL pointer dereference if priv->enable_gpios is NULL. Affects Kernel versions < ba8a26a7ce8617f9f3d6230de34b2302df086b41. 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 manages communication between hardware and software. It provides essential services and functions for the proper functioning of the system. The regulator subsystem within the Kernel is responsible for controlling voltage and current levels for various hardware components. One of the regulators, rt4801, is affected by a vulnerability that can lead to a NULL pointer dereference if priv->enable_gpios is NULL.
Vulnerability Detail
The vulnerability in regulator: rt4801 arises when the priv->enable_gpios pointer is NULL. This can occur due to improper handling of the enable_gpios variable, leading to a NULL pointer dereference. An attacker could potentially exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code with kernel privileges. The impact and attack plausibility of this vulnerability have not been proven. The vulnerability has been fixed in Linux Kernel version v5.10.46 by commit ba8a26a7ce8617f9f3d6230de34b2302df086b41.
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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in regulator: rt4801 within the Kernel can lead to a NULL pointer dereference if priv->enable_gpios is NULL. It is recommended to update the Linux Kernel to version v5.10.46 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from a denial-of-service condition to arbitrary code execution with kernel privileges.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
There is no information available regarding exploitation of this vulnerability in the wild.
The only known mitigation is to update the Linux Kernel to version v5.10.46 or later.
You can refer to the vulnerability details in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000994.json) for more information.
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.
