Vulnerability in brcmfmac Kernel Package: Release Firmwares in the brcmf_pcie_setup Error Path
Summary
GSD-2022-1001590: brcmfmac: pcie: Release firmwares in the brcmf_pcie_setup error path. Affects Kernel versions >= 82f93cf46d6007ffa003b2d4a2834563b6b84d21, < 4e0b507597e1a86e9b4c056ab274c427223cf8ea. 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 brcmfmac package is a kernel module that provides support for Broadcom wireless devices. It is responsible for managing the communication between the kernel and the firmware of these devices. The package is a part of the Linux Kernel ecosystem and is used in various Linux distributions. However, a vulnerability has been discovered in the brcmfmac package that affects its PCIe functionality.
Vulnerability Detail
The vulnerability in the brcmfmac PCIe functionality occurs when firmwares are not properly released in the brcmf_pcie_setup error path. This can lead to resource leaks and potential memory corruption issues. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial of service. The vulnerability was introduced in version v5.4 of the Linux Kernel and has been fixed in version v5.16.19.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.16.19 or later. This can be done by downloading the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the instructions provided. Once the updated kernel is installed, the vulnerability should be mitigated.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
If updating the Linux Kernel is not immediately feasible, a possible workaround is to avoid triggering the brcmf_pcie_setup error path. This can be achieved by ensuring that the necessary resources and conditions for the error path are not met. However, this workaround may not provide complete protection and it is still recommended to update the kernel as soon as possible.
Conclusion
The vulnerability in the brcmfmac PCIe functionality can lead to resource leaks and potential memory corruption issues. It is recommended to update the Linux Kernel to version v5.16.19 or later to fix this vulnerability. If immediate update is not possible, the suggested workaround can be implemented. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial of service by exploiting the brcmfmac PCIe functionality.
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 any open-source vulnerabilities, including this one.
At the time of this report, there is no known public exploit for this vulnerability. However, it is still important to apply the recommended fixes to ensure the security of your system.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is important to update the Linux Kernel to mitigate the risk of remote exploitation.
The primary mitigation for this vulnerability is to update the Linux Kernel to the fixed version. However, if immediate kernel update is not possible, the suggested workaround can be implemented to reduce the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.