Vulnerability in Bluetooth hci_uart Package
Summary
GSD-2022-1001517: Bluetooth: hci_uart: add missing NULL check in h5_enqueue. Affects Kernel versions >= d9dd833cf6d29695682ec7e7924c0d0992b906bc, < e6b6c904c0f88588b6a3ace20e4c0d61eab124f8. 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 hci_uart package is a component of the Linux Kernel ecosystem. It provides functionality for Bluetooth communication over UART (Universal Asynchronous Receiver-Transmitter) interfaces. This vulnerability affects versions 5.15 to 5.16.18 of the Linux Kernel. The package is vulnerable to a missing NULL check in the h5_enqueue function.
Vulnerability Detail
The vulnerability arises from a missing NULL check in the h5_enqueue function of the Bluetooth hci_uart package. This oversight could potentially be exploited by an attacker to execute arbitrary code or trigger a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version 5.15 of the Linux Kernel and has been fixed in version 5.16.19.
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 workaround has been provided for this vulnerability.
Conclusion
The Bluetooth hci_uart package in the Linux Kernel is vulnerable to a missing NULL check in the h5_enqueue function. This vulnerability could potentially lead to arbitrary code execution or denial-of-service attacks. It is crucial to update to Linux Kernel version 5.16.19 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.
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 alert you in real-time.
Yes, the vulnerability has been fixed in Linux Kernel version 5.16.19. It is recommended to update to this version or later to mitigate the vulnerability.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
There are no known instances of this vulnerability being exploited at the moment. However, it is always recommended to apply security updates promptly to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
