Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-19738Published 2026-10-11

CVE-2026-19738 — zephyrproject zephyr

medium

As of 2026-10-11, CVE-2026-19738 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 6.5, EPSS 0.1% (97.9th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-19738 as of 2026-10-11; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.5/10Medium
EPSS
0.1%Higher than 97.9% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
7.2/10Threadlinqs triage score
Published
CVSS v3.1 6.5 (MEDIUM) · EPSS 0.1% (higher than 97.9% of all scored CVEs) · Priority 7.2/10 · Published 2026-10-11

Last updated:

What is CVE-2026-19738?

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.

The record classifies CVE-2026-19738 under weakness class CWE-401. Its CVSS v3 base vector states that the flaw is reachable from an adjacent network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 39 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.5 — MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 97.9% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
7.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-11

Is CVE-2026-19738 being exploited?

It currently carries a trending score of 54 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-19738

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/fde17f2c3de0118f3796c2a83958ee4ce4b5efd6. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-19738

No threat campaign in the Threadlinqs corpus currently references CVE-2026-19738, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references