Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-15460Published 2026-09-09

CVE-2026-15460 — zephyrproject zephyr

medium

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

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

Last updated:

What is CVE-2026-15460?

The Bluetooth Classic (BR/EDR) L2CAP receive handler bt_l2cap_br_recv() in subsys/bluetooth/host/classic/l2cap_br.c dispatched inbound data PDUs based only on the destination channel ID, without checking that the target channel had reached the BT_L2CAP_CONNECTED state. A dynamic channel is assigned its RX CID and added to the connection's channel list while still in BT_L2CAP_CONNECTING (and later BT_L2CAP_CONFIG) — before configuration completes and, for PSMs that require security, before the peer is authenticated (l2cap_br_conn_req()). Because the channel is already findable by bt_l2cap_br_lookup_rx_cid() during this window, a remote peer within radio range can send a data PDU addressed to that CID and have it processed on a not-yet-established channel. The dispatch keys off channel fields (BR_CHAN(chan)->rx.mode, rx.mps) that are only initialized during configuration by l2cap_br_conf(); since channel objects are pooled and bt_l2cap_br_chan_del() does not reset rx.mode or the reassembly buffer _sdu, a reused channel can carry stale state into the CONNECTING window and route the frame into the retransmission/flow-control path (bt_l2cap_br_ret_fc_recv()) with stale parameters and a possibly stale _sdu pointer. The impact is delivery of attacker data to upper-layer protocol handlers on a half-open (and possibly unauthenticated) channel, plus operation on stale or partially initialized channel state on reused channel objects — leading to channel/link teardown (denial of service) and, in the stale-_sdu case, a dangling-pointer condition. The fix adds an explicit BR_CHAN(chan)->state < BT_L2CAP_CONNECTED guard that drops any data received before the channel is fully connected.

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

Severity and exploitation probability

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

Is CVE-2026-15460 being exploited?

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

Affected products and versions

How to fix CVE-2026-15460

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/2738ee921ba61ba2e644c95bceba302896dd8c19. 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-15460

No threat campaign in the Threadlinqs corpus currently references CVE-2026-15460, 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