zephyrproject-rtos Zephyr up to 4.1.0 Bluetooth Low Energy integer overflow

Summaryinfo

A vulnerability was found in zephyrproject-rtos Zephyr up to 4.1.0. It has been rated as problematic. Impacted is an unknown function of the component Bluetooth Low Energy Handler. The manipulation leads to integer overflow. This vulnerability is traded as CVE-2025-10456. Access to the local network is required for this attack to succeed. There is no exploit available.

Detailsinfo

A vulnerability was found in zephyrproject-rtos Zephyr up to 4.1.0. It has been rated as problematic. This issue affects an unknown function of the component Bluetooth Low Energy Handler. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is integrity, and availability. The summary by CVE is:

A vulnerability was identified in the handling of Bluetooth Low Energy (BLE) fixed channels (such as SMP or ATT). Specifically, an attacker could exploit a flaw that causes the BLE target (i.e., the device under attack) to attempt to disconnect a fixed channel, which is not allowed per the Bluetooth specification. This leads to undefined behavior, including potential assertion failures, crashes, or memory corruption, depending on the BLE stack implementation.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-10456 since 09/15/2025. The exploitation is known to be easy. The attack needs to approached within the local network. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/29/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-30238). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Project Management Software

Vendor

• zephyrproject-rtos

Name

• Zephyr

Version

• 4.0
• 4.1.0

License

• open-source

Website

• Product: https://github.com/zephyrproject-rtos/zephyr/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion