Vulnerability in Kernel: pfuze100 - Refcount Leak in pfuze_parse_regulators_dt
Summary
GSD-2022-1004013: regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt. Affects Kernel versions >= 3784b6d64dc52ed3fbebad61a85ab9b7a687a167, < 6ca675f4abbc74bc991d154a1ecc8b384dc2aae4. 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 fundamental component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with hardware. The pfuze100 regulator driver is used to control power regulators on certain devices. This vulnerability, identified as GSD-2022-1004013, involves a refcount leak in the pfuze_parse_regulators_dt function of the pfuze100 driver.
Vulnerability Detail
The pfuze_parse_regulators_dt function in the pfuze100 regulator driver suffers from a refcount leak. This vulnerability was introduced in version v3.12 of the Linux Kernel and fixed in version v4.14.283. An attacker could potentially exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code with elevated privileges. The vulnerability arises due to improper handling of reference counts, leading to a resource leak. By carefully crafting a malicious input, an attacker could exhaust system resources or manipulate the reference count to gain unauthorized access.
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
No specific workaround has been provided for this vulnerability.
Conclusion
In conclusion, the Kernel's pfuze100 regulator driver is vulnerable to a refcount leak in the pfuze_parse_regulators_dt function. This vulnerability can potentially lead to a denial-of-service condition or arbitrary code execution. It is crucial to update the Linux Kernel to version v4.14.283 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially lead to a denial-of-service condition or allow an attacker to 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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, no known exploits have been identified for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to untrusted networks or if the attacker has already gained access to the system through other means.
For more details about this vulnerability, including the specific commit that fixes it, you can refer to the source link provided in the vulnerability details section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
