Vulnerability in Kernel package: Input: sparcspkr - fix refcount leak in bbc_beep_probe
Summary
GSD-2022-1004002: Input: sparcspkr - fix refcount leak in bbc_beep_probe. Affects Kernel versions >= 9c1a5077fdca99356c891af37931e537dea874f5, < f13064b0f2c651a3fbb0749932795c6fd21556a8. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for communication between hardware and software. The sparcspkr module within the Kernel package is responsible for handling the speaker on SPARC-based systems. It allows for generating beeping sounds for various purposes. However, a vulnerability has been discovered in the bbc_beep_probe function of the sparcspkr module, leading to a refcount leak.
Vulnerability Detail
The vulnerability in the bbc_beep_probe function of the sparcspkr module results in a refcount leak. This can potentially lead to resource exhaustion and impact system stability. An attacker may be able to exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v2.6.26 of the Kernel package and has been fixed in version v4.14.283.
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 mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel package's sparcspkr module, specifically in the bbc_beep_probe function, can lead to resource exhaustion and potential system instability. It is crucial to update the Kernel package to version v4.14.283 or later to mitigate this vulnerability. No specific workaround has been provided. For additional support and assistance, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and system instability. It may also allow attackers to cause a denial-of-service (DoS) condition or 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 potential vulnerabilities.
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.
The exact exploitability of this vulnerability depends on various factors, such as system configuration and network accessibility. However, in general, an attacker would need local access to the system to exploit this vulnerability.
For further support and assistance with vulnerability remediation, you can reach out to info@devnack.com. Our team of experts is available to provide guidance and help address any concerns.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
