The Bluetooth Link Layer Control Procedure (LLCP) implementation for Connected Isochronous Stream (CIS) creation retains an RX node (ctx->node_ref.rx, marked NODE_RX_TYPE_RETAIN) so it can later be reused as the host notification — on the peripheral while awaiting the Host's reply to an LL_CIS_REQ, and on the central for the whole duration of a locally initiated CIS Create. In subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c, the "invalid PDU received" paths of llcp_rp_cc_rx() and llcp_lp_cc_rx() terminated the connection and completed the procedure without releasing that retained node, breaking the invariant checked in llcp_lr_check_done() and llcp_rr_check_done() and orphaning the node's memory.
A peer device within radio range can reach this with a single extra LL Control PDU on an unauthenticated, unencrypted ACL link. Against a peripheral, the attacker sends a valid LL_CIS_REQ and then, before the Host replies, any unrelated LL Control PDU (for example LL_VERSION_IND), which ull_cp_rx() routes into the active remote procedure. Against a central performing a CIS Create, a malicious peripheral answers with LL_UNKNOWN_RSP for CIS_REQ, which is dispatched into the active local procedure. No pairing, encryption or user interaction is required; the code is compiled in when CONFIG_BT_CTLR_PERIPHERAL_ISO or CONFIG_BT_CTLR_CENTRAL_ISO is enabled.
In default builds (CONFIG_BT_CTLR_ASSERT_DEBUG is default y) the retained-node assertion fires immediately, producing a controller fatal error and, typically, a system reset from one injected PDU. With the development assertions disabled, each attempt permanently loses one node from the controller's small LL notification pool (LL_PDU_RX_CNT, 2 * CONFIG_BT_CTLR_LLCP_CONN) together with its memq_link_t; repeating the connect-attack-reconnect cycle exhausts the pool, after which notification allocation always fails, RX flow control stalls, and the non-disableable LL_ASSERT_ERR() in llcp_lp_cc_flush() faults. The impact is limited to availability — the leaked node is orphaned, never reused or double-freed — and recovery requires a reboot.
{
"cna_assigner": "zephyr",
"cwe_ids": [
"CWE-401"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/19xxx/CVE-2026-19738.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "3.4.0"
},
{
"fixed": "4.5.0"
}
],
"source": "AFFECTED_FIELD"
}
]
}"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-19738.json"
[
{
"deprecated": false,
"digest": {
"line_hashes": [
"135035397242682923938940796715808736887",
"316605279232163874252627673590778793588",
"91980403134506916960688919468744312587",
"328547317025466234453595596329886374721",
"43191210951706079702434836035993313191",
"95431937156492165289850287182280951177",
"88876095488478896349485344239203440478",
"169083117063003347493621596946790968389"
],
"threshold": 0.9
},
"id": "CVE-2026-19738-6b5b6364",
"signature_type": "Line",
"signature_version": "v1",
"source": "https://github.com/zephyrproject-rtos/zephyr/commit/fde17f2c3de0118f3796c2a83958ee4ce4b5efd6",
"target": {
"file": "subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c"
}
},
{
"deprecated": false,
"digest": {
"function_hash": "51729755454229116008165208409422380583",
"length": 638
},
"id": "CVE-2026-19738-6ce1f8f6",
"signature_type": "Function",
"signature_version": "v1",
"source": "https://github.com/zephyrproject-rtos/zephyr/commit/fde17f2c3de0118f3796c2a83958ee4ce4b5efd6",
"target": {
"file": "subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c",
"function": "llcp_rp_cc_rx"
}
},
{
"deprecated": false,
"digest": {
"function_hash": "51836658487746152832899748647758249801",
"length": 539
},
"id": "CVE-2026-19738-a7731fcb",
"signature_type": "Function",
"signature_version": "v1",
"source": "https://github.com/zephyrproject-rtos/zephyr/commit/fde17f2c3de0118f3796c2a83958ee4ce4b5efd6",
"target": {
"file": "subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c",
"function": "llcp_lp_cc_rx"
}
}
]
"2026-10-13T07:01:33Z"