Critical Vulnerability in Linux Package: Bluetooth L2CAP Div-by-Zero Issue
Summary
DEBIAN-CVE-2024-36968: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init() l2cap_le_flowctl_init() can cause both div-by-zero and an integer overflow since hdev->le_m... Affects linux versions < 6.8.11-1. Fixed in 6.8.11-1. 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 package is a core component of the Debian operating system, responsible for managing hardware interactions and system processes. It provides essential functionalities, including device management, process scheduling, and memory management. This vulnerability specifically affects the Bluetooth subsystem, which facilitates wireless communication between devices. The flaw can lead to severe system instability and potential crashes due to improper handling of Bluetooth connections.
Vulnerability Detail
In the Linux kernel, a vulnerability has been identified in the Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) implementation. The issue arises in the function l2cap_le_flowctl_init(), where a division by zero can occur if the 'le_mtu' (Maximum Transmission Unit) value is not validated correctly. This can lead to both a division error and an integer overflow, potentially causing system crashes or undefined behavior. The vulnerability is triggered when invalid MTU values are processed, which can disrupt Bluetooth communication and overall system stability.
How To Fix
Minimum fixed version
6.8.11-1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade linuxTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can disable Bluetooth functionality until the package is updated. This can be done by executing the command:
sudo systemctl stop bluetooth.service
However, this is not a permanent solution and should only be used until the patch is applied.
Conclusion
The identified vulnerability in the Linux package poses significant risks to system stability and Bluetooth communication. It is crucial for users to update their systems to the patched version to mitigate these risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for linux →
FAQ
The vulnerability is a division by zero error in the Bluetooth L2CAP implementation, which can lead to system crashes.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.
Exploiting this vulnerability can lead to system instability, crashes, and potential data loss due to improper handling of Bluetooth connections.
Yes, updating the Linux package to version 6.8.11-1 or later will permanently fix the vulnerability.
If you cannot update immediately, consider disabling Bluetooth functionality as a temporary workaround until the patch is applied.
References
Related vulnerabilities
Recent vulnerabilities recorded for linux.
