Vulnerability in Kernel package: usb: misc: brcmstb-usb-pinmap
Summary
UVI-2021-1001022: usb: misc: brcmstb-usb-pinmap: check return value after calling platform_get_resource(). Affects Kernel versions >= 517c4c44b32372d2fdf4421822e21083c45e89f9, < 2147684be1ebdaf845783139b9bc4eba3fecd9e4. 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 critical component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services and interfaces for hardware devices, including USB controllers. The brcmstb-usb-pinmap module within the Kernel package is specifically designed for Broadcom Set-Top Box (STB) USB controllers. These controllers enable communication between the STB and USB devices such as keyboards, mice, and storage devices.
Vulnerability Detail
The identified vulnerability in the brcmstb-usb-pinmap module involves a failure to check the return value after calling the platform_get_resource() function. This oversight can potentially lead to various security issues. Attackers may exploit this vulnerability to execute arbitrary code, escalate privileges, or cause denial-of-service conditions. The impact and attack plausibility of this vulnerability have not been fully proven yet.
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
As a temporary workaround, users can disable or disconnect any USB devices connected to the Broadcom STB USB controller. This reduces the attack surface and mitigates the risk of exploitation. However, this workaround may impact the functionality of USB-dependent features on the system.
Conclusion
The identified vulnerability in the brcmstb-usb-pinmap module of the Kernel package poses potential security risks, including arbitrary code execution and privilege escalation. It is crucial to update the Linux Kernel package to version v5.12.11 or later to mitigate these risks. Users can also utilize Vulert's playground to check if their systems are affected by this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's capabilities and intentions. It may lead to arbitrary code execution, privilege escalation, or denial-of-service conditions.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will provide real-time alerts for open-source vulnerabilities.
At the time of this report, no known exploits for this vulnerability have been disclosed. However, it is crucial to apply the recommended updates to mitigate potential risks.
While updating the Kernel package is the primary security measure, users can also implement general security practices such as restricting physical access to the system, using strong passwords, and regularly monitoring for suspicious activities.
For more detailed information about this vulnerability, including technical aspects and the fix implementation, please refer to the source link provided in the database_specific section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.