Vulnerability in spi: uniphier package - Reference Count Leak in uniphier_spi_probe()
Summary
GSD-2022-1000585: spi: uniphier: fix reference count leak in uniphier_spi_probe(). Affects Kernel versions >= 28d1dddc59f6b7fc085093e7c1e978b33f0caf4c, < dd00b4f8f768d81c3788a8ac88fdb3d745e55ea3. 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 spi: uniphier package is a component of the Linux Kernel ecosystem. It provides support for the SPI (Serial Peripheral Interface) bus on Uniphier SoCs (System-on-Chips). The SPI bus is commonly used for communication between microcontrollers and peripheral devices. The uniphier_spi_probe() function is responsible for initializing the SPI controller and registering it with the SPI framework. However, a reference count leak vulnerability has been identified in this function.
Vulnerability Detail
The reference count leak vulnerability in uniphier_spi_probe() allows an attacker to cause a reference count imbalance, potentially leading to a use-after-free or other memory corruption issues. By exploiting this vulnerability, an attacker may be able to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. The vulnerability was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.15.22.
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 available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
In conclusion, the spi: uniphier package in the Linux Kernel is vulnerable to a reference count leak in the uniphier_spi_probe() function. This vulnerability can potentially lead to memory corruption and various security risks. It is crucial to update the Linux Kernel to version v5.15.22 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service condition.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The exact conditions for remote exploitation of this vulnerability are not specified in the available information. However, it is always recommended to apply security patches and updates to mitigate any potential remote exploitation risks.
The recommended solution is to update the Linux Kernel to the latest version. Alternative solutions may include applying patches or modifications specifically addressing the reference count leak in uniphier_spi_probe(). However, these alternative solutions may not provide the same level of assurance and compatibility as the official Kernel update.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
