Bluetooth cmtp: File Refcount Fix
Summary
UVI-2021-1000707: Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails. Affects Kernel versions < 61a811e8f5229264b822361f8b23d7638fd8c914. 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 cmtp (Connection Manager Transport Protocol) is a component of the Linux Kernel that handles file transfers over Bluetooth connections. It provides functionality for attaching devices and managing file transfers. However, a vulnerability has been discovered in the cmtp module that can lead to a file refcount issue when attaching a device fails.
Vulnerability Detail
The vulnerability in the Bluetooth cmtp module occurs when the cmtp_attach_device function fails to properly handle file refcounts. This can result in a file refcount leak, leading to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability by repeatedly attempting to attach a malicious device, causing the system to exhaust its file resources and potentially crash.
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
There is no specific workaround provided for this vulnerability. However, users can mitigate the risk by updating their Linux Kernel to the recommended version.
Conclusion
The Bluetooth cmtp module in the Linux Kernel is vulnerable to a file refcount issue when attaching devices fails. This can lead to resource exhaustion and potential denial-of-service attacks. To mitigate the vulnerability, it is crucial to update the Linux Kernel to version v4.4.271 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to crash the system by repeatedly attempting to attach a malicious device.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for open-source vulnerabilities in real-time.
Yes, a patch is available in the Linux Kernel version v4.4.271. It is recommended to update your Kernel to this version or later to fix the vulnerability.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the recommended fix to mitigate the risk.
The recommended mitigation for this vulnerability is to update the Linux Kernel to the recommended version. There are no specific mitigations available without updating the Kernel.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
