Vulnerability in Kernel package: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
Summary
GSD-2022-1004618: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe. Affects Kernel versions >= 0b741b8234c86065fb6954d32d427b3f7e14756f, < 30bbfeb480ae8b5ee43199d72417b232590440c2. 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 fundamental component of the Linux operating system. It provides the core functionality and interfaces for various hardware devices, drivers, and system services. The bcm (Broadcom) subsystem within the Kernel package includes support for Broadcom's system-on-a-chip (SoC) devices. The brcmstb_pm module is responsible for power management on bcm SoCs. However, a refcount leak vulnerability has been identified in the brcmstb_pm_probe function of the pm-arm module, which can lead to resource exhaustion and potential system instability.
Vulnerability Detail
The refcount leak vulnerability in brcmstb_pm_probe arises due to improper handling of reference counts when probing the brcmstb_pm module. This can result in a gradual accumulation of unused resources, leading to resource exhaustion and potential system crashes or instability. An attacker with local access to the affected system could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or escalate privileges. The vulnerability was introduced in version v4.15 of the Linux Kernel and has been fixed in version v5.10.127.
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 known workarounds are available for this vulnerability.
Conclusion
The refcount leak vulnerability in the brcmstb_pm_probe function of the pm-arm module in the Kernel package can lead to resource exhaustion and potential system instability. It is recommended to update the Linux Kernel to version v5.10.127 or later to mitigate this vulnerability. No known workarounds are available. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential system instability, which may result in system crashes or denial-of-service (DoS) conditions. An attacker with local access to the affected system could potentially exploit this vulnerability to escalate 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 to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities, including this one, are found.
Yes, the vulnerability has been fixed in version v5.10.127 of the Linux Kernel. It is recommended to update to this version or a later one to mitigate the vulnerability.
There are no known public exploits specifically targeting this vulnerability at the time of this report. However, it is always advisable to promptly apply security patches to mitigate any potential risks.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2022-1004618, and the database entry can be accessed at: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004618.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
