CVE-2025-23050
BaseFortify
Publication date: 2025-10-31
Last updated on: 2025-11-04
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qt | qt | 5.15.19 |
| qt | qt | 6.8.2 |
| qt | qt | 6.9.0 |
| qt | qt | 6.5.9 |
| qt | qt | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-23050 is a vulnerability in the QLowEnergyController component of the Qt Bluetooth module on Linux. It occurs when malformed Bluetooth ATT commands are sent from an external Bluetooth Low Energy device, causing the software to perform an out-of-bounds read or a division by zero error. This happens because the QLowEnergyController mishandles these malformed commands when using the Bluetooth Kernel API backend, potentially leading to crashes or other security issues. The vulnerability affects multiple Qt versions before they were patched. [2]
How can this vulnerability impact me? :
This vulnerability can allow an external Bluetooth Low Energy device to send malformed ATT commands that cause the affected Qt application to crash or behave unpredictably due to out-of-bounds reads or division by zero errors. This could lead to denial of service or other security impacts depending on the context in which the vulnerable component is used. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves malformed Bluetooth ATT commands sent from an external Bluetooth Low Energy device causing out-of-bounds reads or division by zero errors in QLowEnergyController. Detection would involve monitoring Bluetooth Low Energy traffic for malformed ATT commands or unusual Bluetooth L2CAP socket activity. Specific commands are not provided in the resources, but generally, tools like 'btmon' on Linux can be used to capture and analyze Bluetooth traffic to detect malformed ATT commands. Additionally, checking the BlueZ version and Qt version in use can help assess exposure. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating Qt to versions 6.9.0, 6.8.2, 6.5.9, or 5.15.19 where the vulnerability is fixed. If updating is not immediately possible, ensure that the BlueZ runtime version is 5.42 or higher for central roles and 5.56 or higher for peripheral roles to avoid using the vulnerable Bluetooth Kernel API backend. Also, avoid enabling the environment variable QT_BLUETOOTH_USE_KERNEL_PERIPHERAL if possible. Applying patches provided by the Qt project is recommended. [2]