CVE-2025-10456High· 7.1▾ TwilightA 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 dis…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 39.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
0.2%
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.
zephyr <= 4.1.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2025-10458High· 7.6Parameters are not validated or sanitized, and are later used in various internal operations.
CVE-2025-7403High· 7.6Unsafe handling in bt_conn_tx_processor causes a use-after-free, resulting in a write-before-zero
CVE-2025-10457Medium· 4.3The function responsible for handling BLE connection responses does not verify whether a response is expected—that is, whether the device has initiated a connection request
CVE-2025-1675High· 8.2The function dns_copy_qname in dns_pack.c performs performs a memcpy operation with an untrusted field and does not check if the source buffer is large enough to contain the copied data.
CVE-2025-2962High· 7.5A denial-of-service issue in the dns implemenation could cause an infinite loop.
CVE-2025-1673High· 8.2A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation.