Refcount Leak in pfuze_parse_regulators_dt in Kernel
Summary
GSD-2022-1002766: regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt. Affects Kernel versions >= 3784b6d64dc52ed3fbebad61a85ab9b7a687a167, < 49d785baeb91568332197be356d138e5e59c7ddb. 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 Kernel is a crucial component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The vulnerability in question, identified as GSD-2022-1002766, specifically affects the regulator subsystem within the Kernel. The regulator subsystem is responsible for managing voltage regulators on various hardware platforms. The pfuze100 regulator driver is impacted by a refcount leak in the pfuze_parse_regulators_dt function, which can lead to resource leaks and potential system instability.
Vulnerability Detail
The vulnerability arises from a refcount leak in the pfuze_parse_regulators_dt function of the pfuze100 regulator driver. When parsing the device tree (DT) representation of regulators, the function fails to properly release the reference count of the regulator, resulting in a resource leak. This can lead to various issues, including memory leaks, resource exhaustion, and potential system crashes. An attacker with local access to the system may be able to exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges.
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 disable the affected regulator driver (pfuze100) if it is not required for their system's operation. This can be achieved by modifying the device tree (DT) representation to exclude the regulator node associated with the pfuze100 driver. However, this workaround may result in the loss of certain functionality or features that rely on the affected regulator.
Conclusion
In conclusion, the refcount leak in pfuze_parse_regulators_dt in the Kernel's pfuze100 regulator driver can lead to resource leaks, memory leaks, and potential system crashes. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. Alternatively, users can disable the affected regulator driver as a temporary workaround, although this may result in the loss of certain functionality. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource leaks, memory leaks, and potential system crashes. An attacker with local access to the system may be able to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities are present.
Yes, a fix for this vulnerability is available in Linux Kernel version v5.18.3. Users are advised to update their Kernel to this version or a later one to mitigate the risk.
Yes, as a workaround, you can disable the affected regulator driver (pfuze100) if it is not required for your system's operation. However, this may result in the loss of certain functionality or features that rely on the affected regulator.
You can find more information about this vulnerability in the GSD-2022-1002766 entry of the GSD Database maintained by the Cloud Security Alliance. The entry provides additional details, including the source of the vulnerability and the commit that fixed it.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
