CVE-2026-5068

published 9 Jun 2026 · updated 15 Oct 2026

bt: l2cap le coc: remote oob write via seg counter stored in net_buf user_data

7.6HighCVSS 7.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.3.1.

A remote, unauthenticated BLE peer can trigger a 2-byte out-of-bounds write in the Bluetooth host during L2CAP LE CoC SDU reassembly. When the application enables segmentation (via chan_ops.alloc_buf) and the chosen RX pool has a user_data_size smaller than 2 bytes, the segmentation counter stored in the net_buf user_data area is written out of bounds in l2cap_chan_le_recv_seg (subsys/bluetooth/host/l2cap.c). The observed effects are an AddressSanitizer abort and, without ASan, heap corruption / fatal error.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
zephyrproject-rtos>=1.14.0 <4.3.14.3.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-5068 severity on Zeptric[![CVE-2026-5068](https://zeptric.io/badge/cve/CVE-2026-5068.svg)](https://zeptric.io/cve/CVE-2026-5068)