Bluetooth cmtp File Refcount Vulnerability in Linux Kernel
Summary
GSD-2021-1000658: Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails. Affects Kernel versions < f8be26b9950710fe50fb45358df5bd01ad18efb7. 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 Linux Kernel is a widely used open-source operating system kernel that serves as the foundation for various Linux distributions. It provides essential functionality and interfaces for hardware, software, and user applications. Bluetooth is a wireless technology commonly used for short-range communication between devices. The cmtp (Connection Manager Transport Protocol) is a Bluetooth protocol used for transferring files between devices. However, a vulnerability has been discovered in the cmtp module of the Linux Kernel.
Vulnerability Detail
The vulnerability in the cmtp module of the Linux Kernel allows an attacker to manipulate file refcounts when the cmtp_attach_device function fails. This can lead to a use-after-free vulnerability, potentially allowing an attacker to execute arbitrary code or cause a denial-of-service condition. The vulnerability was introduced in an unknown version of the Linux Kernel and has been fixed in version v4.19.193 by commit f8be26b9950710fe50fb45358df5bd01ad18efb7.
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 known workaround for this vulnerability. It is recommended to apply the official fix by updating the Linux Kernel.
Conclusion
The Bluetooth cmtp file refcount vulnerability in the Linux Kernel can potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition. It is crucial for users to update their Linux Kernel to version v4.19.193 or later to mitigate this vulnerability. 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 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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system has Bluetooth enabled and is within range of an attacker.
The only known mitigation for this vulnerability is to update the Linux Kernel to the fixed version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
