Refcount Leak in stm32_usbphyc_pll_enable() in Kernel
Summary
GSD-2022-1000502: phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable(). Affects Kernel versions >= 5b1af71280abd82efbe28cd28d553363dfde0a34, < 0ad1a88fa3eb0ded7798f52b79bc33f75fc9a6d2. 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 that manages system resources and facilitates communication between hardware and software. It provides essential functions and services to ensure the proper functioning of the system. The stm32_usbphyc_pll_enable() function is part of the Kernel's phy: stm32 module, which handles the USB physical layer for STM32 microcontrollers. This module enables the USB PHY PLL (Phase-Locked Loop) for STM32 devices, ensuring stable and reliable USB communication.
Vulnerability Detail
The stm32_usbphyc_pll_enable() function in the phy: stm32 module of the Kernel suffers from a refcount leak vulnerability. This vulnerability, identified as GSD-2022-1000502, occurs when the function fails to properly release a reference count, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet.
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 this vulnerability can be mitigated by updating the Kernel, there is no specific workaround available. It is recommended to follow the steps mentioned in the 'how_to_fix' section to resolve the issue.
Conclusion
The refcount leak vulnerability in stm32_usbphyc_pll_enable() in the Kernel's phy: stm32 module can potentially lead to a denial-of-service (DoS) condition. It is crucial to update the Linux Kernel to version v5.16.10 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
The impact of this vulnerability is not yet proven. However, it could potentially lead to a denial-of-service (DoS) condition by exhausting system resources.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert analyzes the manifest file, such as package-lock.json, to detect and alert in real-time for open-source vulnerabilities.
No known exploit for this vulnerability has been reported at this time.
The specific prerequisites for exploiting this vulnerability are not yet known.
No, updating the Kernel to version v5.16.10 or later is necessary to fix this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
