Vulnerability in Kernel package: Input: sparcspkr - fix refcount leak in bbc_beep_probe
Summary
GSD-2022-1004068: Input: sparcspkr - fix refcount leak in bbc_beep_probe. Affects Kernel versions >= 9c1a5077fdca99356c891af37931e537dea874f5, < 2f51db16cb740ff90086189a1ef2581eab665591. 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 interfaces for the system's hardware and software components. The sparcspkr module within the Kernel package handles the system speaker on SPARC-based systems. It allows generating beeping sounds for various purposes, such as system alerts or error notifications. However, a vulnerability has been discovered in the bbc_beep_probe function of the sparcspkr module, leading to a refcount leak. This vulnerability can potentially be exploited by attackers to cause a denial-of-service (DoS) condition or escalate privileges.
Vulnerability Detail
The vulnerability originates from a refcount leak in the bbc_beep_probe function of the sparcspkr module. When this function is called, it fails to properly release the reference count on certain resources, resulting in a leak. An attacker can potentially exploit this vulnerability by repeatedly triggering the bbc_beep_probe function, causing the refcount to increase and potentially leading to resource exhaustion or privilege escalation. The impact and attack plausibility of this vulnerability have not yet been proven.
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, a vulnerability has been identified in the Kernel package, specifically in the sparcspkr module's bbc_beep_probe function. This vulnerability involves a refcount leak and can potentially lead to a denial-of-service condition or privilege escalation. To mitigate this vulnerability, it is crucial to update the Kernel package to version v4.9.318 or later. 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 privilege escalation. However, the exact impact and attack plausibility have not yet been proven.
You can use the Vulert Playground at Vulert 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.
No specific workaround has been provided for this vulnerability. It is recommended to update the Kernel package to the fixed version mentioned earlier.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
There are no known instances of this vulnerability being exploited in the wild. However, it is still important to apply the recommended fix to ensure system security.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
