Zephyr Project RTOS: Thirteen Vulnerabilities in Bluetooth, Networking, and Drivers Disclosed Together
Thirteen vulnerabilities disclosed for Zephyr Project RTOS, impacting Bluetooth, networking, and drivers, with several high-severity flaws reported.

Key findings
- Thirteen CVEs disclosed for Zephyr Project RTOS between Oct 11-14, 2026, impacting Bluetooth, networking, and drivers.
- High-severity flaws include issues in Bluetooth LE host, IPv6 routing, NXP entropy driver, and fuel gauge syscall handlers.
- Multiple vulnerabilities stem from improper handling of radio-reported lengths and buffer overflows in driver components.
- Bluetooth vulnerabilities include issues in HFP AG, AVDTP, Mesh, and LE host data handling.
- Networking vulnerabilities affect IPv6 routing and TCP ISN implementation.
- Low-severity issue in zbus proxy agent involves improper logging of channel names.
On October 11, 2026, a batch of thirteen vulnerabilities was disclosed for the Zephyr Project RTOS, spanning its Bluetooth, networking, and driver components. The disclosures, occurring between October 11 and October 14, 2026, highlight potential weaknesses across several core RTOS functionalities. The vulnerabilities range in severity from Low to High, with several high-severity issues impacting Bluetooth LE host data handling, IPv6 routing, and entropy drivers.
A significant cluster of vulnerabilities affects the Zephyr Project's Bluetooth implementation. CVE-2026-19935, a high-severity flaw, involves improper handling of L2CAP connection-oriented channel data in the Bluetooth LE host, potentially leading to issues during channel teardown. Another high-severity vulnerability, CVE-2026-19736, stems from an insecure entropy driver for NXP MCUX TRNG parts, which passes caller byte counts directly to a vendor SDK routine without proper validation, potentially leading to incorrect entropy generation. Additionally, CVE-2026-19735, a medium-severity issue, relates to the RFC 6528 initial-sequence-number implementation in the TCP stack, where the generation of TCP ISNs was flawed due to a discarded secret key and an improperly latched guard. CVE-2026-19936, a medium-severity vulnerability, exposes a race condition in the Bluetooth Mesh Access-layer delayable message queue due to unsynchronized access to shared lists and work items between two threads. CVE-2026-19939, also medium-severity, concerns a race condition in the AVDTP signaling layer's command timeout mechanism, where responses might not properly cancel pending work items. CVE-2026-19940, another medium-severity flaw, involves a potential use-after-free in the Bluetooth Classic Hands-Free Profile Audio Gateway implementation upon link teardown. Finally, CVE-2026-19740, a medium-severity issue, relates to the Bluetooth LE Controller's Link Layer Control Procedure, where a receive node for PHY update notifications might be retained improperly.
Networking components are also impacted. CVE-2026-19577, a high-severity vulnerability, allows for the resolution of an IPv6 nexthop's link-layer address without verifying if a neighbor cache entry actually has a linked link-layer address, potentially leading to incorrect routing.
Several driver-related vulnerabilities were also disclosed. CVE-2026-19669, a high-severity flaw, resides in user-mode syscall verifiers for fuel gauges, where variable-length arrays are sized directly by a caller-supplied argument, potentially leading to buffer overflows. CVE-2026-75085, a medium-severity issue, affects the STM32WBA IEEE 802.15.4 driver, where the packet length of a received frame is computed without checking if the radio-reported length can hold an FCS, leading to integer underflow due to a uint8_t. CVE-2026-75084, a medium-severity vulnerability in the CC1200 sub-GHz IEEE 802.15.4 driver, involves improper validation of the PHY packet length from the radio's RX FIFO. CVE-2026-75083, a medium-severity flaw in the NXP KW41Z IEEE 802.15.4 driver, computes the payload size as a uint8_t without proper validation of the frame length reported by the radio.
Lastly, CVE-2026-18418, a low-severity vulnerability, affects the zbus proxy agent IPC backend, which logs channel names of rejected inter-domain frames using a plain %s conversion without guaranteeing the array is null-terminated, potentially leading to information disclosure.
The coordinated disclosure, with multiple high-severity vulnerabilities reported, underscores the importance of timely patching and security updates for the Zephyr RTOS. Users are advised to review the specific CVE details and apply necessary updates to mitigate these risks. The batch of disclosures highlights potential weaknesses across core Zephyr RTOS components, emphasizing the need for continuous security vigilance. Vypr Intelligence Vypr Intelligence