Bluetooth: Fix Dangling sco_conn and Use-After-Free in sco_sock_timeout
Summary
GSD-2022-1003600: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout. Affects Kernel versions >= 059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75, < 36c644c63bfcaee2d3a426f45e89a9cd09799318. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. Bluetooth is a wireless communication technology commonly used for short-range data exchange between devices. The vulnerability in the sco_sock_timeout function can lead to a dangling sco_conn and a use-after-free issue. This vulnerability could potentially be exploited by an attacker to execute arbitrary code or cause a denial of service.
Vulnerability Detail
The vulnerability originates from a flaw in the sco_sock_timeout function in the Bluetooth implementation. It was introduced in version v5.10.65 of the Linux Kernel and fixed in version v5.10.121. The issue arises due to improper handling of the sco_conn structure, leading to a dangling pointer and a subsequent use-after-free scenario. An attacker could potentially exploit this vulnerability by sending specially crafted Bluetooth packets, causing the system to crash or executing arbitrary code with kernel-level privileges. The 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
As a workaround, users can disable Bluetooth functionality on their systems until the Kernel package is updated. This can be done by turning off Bluetooth adapters or disabling Bluetooth services in the system settings. However, this workaround may not be feasible for systems that heavily rely on Bluetooth functionality.
Conclusion
The Bluetooth vulnerability in the Kernel package exposes systems to potential crashes and arbitrary code execution. It is crucial to update the Kernel package to version v5.10.121 or later to mitigate the risk. Disabling Bluetooth functionality can serve as a temporary workaround until the update is applied. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from system crashes to arbitrary code execution, potentially leading to a complete compromise of the affected system.
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 Vulert will analyze it for any open-source vulnerabilities, including this Bluetooth vulnerability.
At the time of this report, there are no known public exploits for this vulnerability. However, it is important to promptly update the Kernel package to mitigate the risk.
Disabling Bluetooth functionality on the system can serve as a temporary mitigation until the Kernel package is updated. However, this may not be a feasible solution for systems that heavily rely on Bluetooth.
More information about the fix can be found in the Linux Kernel repository. You can visit the repository at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ and navigate to the commit 36c644c63bfcaee2d3a426f45e89a9cd09799318.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.