CVE-2026-65933 in BT122
Summary
by MITRE • 08/13/2026
A malformed Bluetooth connection request message can cause the BT122 to leak potentially sensitive information. See vulnerability B-E4 in the related paper below.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/13/2026
The vulnerability described represents a critical information disclosure issue within Bluetooth protocol implementations, specifically affecting devices utilizing the BT122 chipset or similar Bluetooth stack components. This flaw manifests through malformed connection request messages that trigger unintended data leakage behaviors in the affected systems. The vulnerability operates at the protocol level where improperly formatted Bluetooth connection requests can cause the device to inadvertently expose sensitive data structures, memory contents, or internal state information that should remain protected from external access.
The technical mechanism underlying this vulnerability involves the Bluetooth stack's insufficient input validation during connection request processing. When a malformed connection request is received, the system fails to properly sanitize or reject the invalid message before proceeding with subsequent processing steps. This inadequate error handling creates an information leak condition where internal memory addresses, uninitialized data buffers, or cryptographic key material may be included in response messages or logged within system traces. The vulnerability aligns with CWE-200, which catalogs weaknesses related to exposure of sensitive information, and represents a classic case of improper input validation leading to information disclosure.
From an operational perspective, this vulnerability poses significant risks to Bluetooth-enabled devices across various industries including automotive systems, industrial control equipment, and consumer electronics. Attackers can exploit this weakness by crafting specific malformed connection requests that trigger the information leakage behavior without requiring physical proximity or complex attack vectors. The impact extends beyond simple data exposure since the leaked information could include device identifiers, memory layouts, cryptographic parameters, or other sensitive metadata that could aid in subsequent attacks. This vulnerability particularly affects systems where Bluetooth connectivity is exposed to untrusted networks or where devices automatically accept incoming connection requests.
The exploitation of this vulnerability can lead to cascading security implications including device fingerprinting, memory layout discovery, and potential privilege escalation opportunities. Security researchers have documented similar patterns in Bluetooth implementations where protocol parsing errors result in information disclosure, making this issue consistent with established attack patterns found in the cybersecurity community. Organizations should consider implementing network segmentation controls around affected Bluetooth devices and ensuring that connection request validation is strengthened through proper input sanitization mechanisms. The vulnerability also highlights the importance of robust error handling in embedded systems and demonstrates how seemingly minor protocol parsing issues can result in significant security implications.
Mitigation strategies should focus on strengthening input validation procedures within Bluetooth stack implementations, implementing proper error handling for malformed messages, and ensuring that connection request processing does not expose internal system information. Organizations should conduct thorough vulnerability assessments of their Bluetooth-enabled devices to identify potential exposure to similar issues, particularly those involving protocol-level parsing errors that could lead to information leakage. The remediation process typically involves updating firmware or software components that contain the vulnerable Bluetooth stack implementations, with particular attention to ensuring that error conditions do not result in sensitive data exposure during connection establishment processes. This vulnerability serves as a reminder of the critical importance of secure coding practices and thorough testing of protocol implementations against malformed inputs, particularly in embedded systems where resource constraints may impact security controls implementation.