Vulnerability in Kernel package: Input: sparcspkr - fix refcount leak in bbc_beep_probe
Summary
GSD-2022-1003575: Input: sparcspkr - fix refcount leak in bbc_beep_probe. Affects Kernel versions >= 9c1a5077fdca99356c891af37931e537dea874f5, < 6e07ccc7d56130f760d23f67a70c45366c07debc. 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 package is a crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The sparcspkr module within the Kernel package is responsible for handling beep sounds on SPARC-based systems. However, a vulnerability has been discovered in the bbc_beep_probe function, which can lead to a refcount leak. This vulnerability could potentially be exploited by attackers to cause a denial-of-service (DoS) condition or execute arbitrary code on the affected system.
Vulnerability Detail
The vulnerability in the bbc_beep_probe function of the sparcspkr module allows for a refcount leak. This occurs when the function fails to properly release resources, resulting in a reference count that is not decremented. An attacker could exploit this vulnerability by repeatedly triggering the bbc_beep_probe function, causing the refcount to increase and potentially leading to resource exhaustion or memory leaks. The impact of this vulnerability could range from a DoS condition to arbitrary code execution, depending on how it is leveraged.
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 →
Conclusion
In conclusion, the Kernel package is vulnerable to a refcount leak in the bbc_beep_probe function of the sparcspkr module. This vulnerability can lead to resource exhaustion, memory leaks, or even arbitrary code execution. It is crucial to update the Linux Kernel package to version v5.10.121 or later, which includes the necessary fix. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a denial-of-service (DoS) condition to potential arbitrary code execution on the affected system.
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 in real-time to identify any open-source vulnerabilities, including this one.
At the moment, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel package to the latest version that includes the fix.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to the internet and the necessary conditions are met for an attacker to trigger the bbc_beep_probe function.
There are no known instances of this vulnerability being exploited in the wild at this time. However, it is important to apply the necessary updates to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
