Deadlock Vulnerability in Bluetooth Package
Summary
GSD-2021-1000264: Bluetooth: avoid deadlock between hci_dev->lock and socket lock. Affects Kernel versions >= eab2404ba798a8efda2a970f44071c3406d94e57, < 332e69eb3bd90370f2d9f2c2ca7974ff523dea17. 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 Bluetooth package is a component of the Linux Kernel ecosystem that provides support for Bluetooth functionality. It enables communication between devices using Bluetooth technology. The package includes various modules and drivers that facilitate Bluetooth operations. However, a vulnerability has been discovered in the package that can lead to a deadlock between the hci_dev->lock and socket lock.
Vulnerability Detail
The identified vulnerability in the Bluetooth package can result in a deadlock scenario where the hci_dev->lock and socket lock become deadlocked. This deadlock can potentially impact the stability and performance of the system. The vulnerability was introduced in version v5.7 of the Linux Kernel and has been fixed in version v5.12.4. The actual impact and attack plausibility of this vulnerability have not been 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
No specific workaround has been provided for this vulnerability.
Conclusion
The identified deadlock vulnerability in the Bluetooth package of the Linux Kernel can potentially impact system stability and performance. It is crucial to update the Linux Kernel to version v5.12.4 or later to mitigate 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 is not yet proven. However, it can potentially lead to system instability and performance issues.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and the playground will provide real-time alerts for open-source vulnerabilities.
No known exploit has been reported for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.12.4 or later, which includes the fix for this vulnerability.
For more details about this vulnerability, you can refer to the source link provided in the database-specific information section of the vulnerability report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
