CVE-2026-15460

Channel teardown via premature L2CAP data dispatch

Published Sep 9, 2026 · Updated Sep 9, 2026

Improper lifecycle handling in Zephyr RTOS before 4.4.2 allows physically proximate attackers to interrupt Bluetooth links. bt_l2cap_br_recv() dispatches data by destination channel ID before the channel reaches BT_L2CAP_CONNECTED, so pooled channels can expose stale receive-mode and reassembly state. A peer within Bluetooth Classic radio range can inject data into a half-open channel without prior authentication, causing channel or link teardown and a dangling-pointer condition.

CVSS severity5.4
Medium
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper lifecycle handling in Zephyr RTOS before 4.4.2 allows physically proximate attackers to interrupt Bluetooth links. bt_l2cap_br_recv() dispatches data by destination channel ID before the channel reaches BT_L2CAP_CONNECTED, so pooled channels can expose stale receive-mode and reassembly state. A peer within Bluetooth Classic radio range can inject data into a half-open channel without prior authentication, causing channel or link teardown and a dangling-pointer condition.

The record

CVE
CVE-2026-15460
Published
Sep 9, 2026
Updated
Sep 9, 2026
Vendor
Zephyr Project
Product
Zephyr RTOS
Classifications
CWE-666, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 9, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.6.0 <4.4.2

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Zephyr Project · Zephyr RTOSversion=1.6.0 <4.4.2

Published CVSS scores

5.4Zephyr ProjectCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-666Operation on Resource in Wrong Phase of Lifetime
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo