CVE-2026-10593 Remotely triggerable NULL-pointer dereference in Bluetooth LE Audio BAP unicast client QoS-state handling
A remote attacker can crash a Zephyr-based Bluetooth LE Audio device by sending malformed state notifications, causing a null pointer dereference.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-10593?
CVE-2026-10593 is a medium-severity vulnerability in Zephyrproject Zephyr, published on 28 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
The Zephyr Bluetooth LE Audio Basic Audio Profile (BAP) unicast client mishandles peer-supplied ASE state notifications. In unicast_client_ep_qos_state() (subsys/bluetooth/audio/bap_unicast_client.c), the handler writes attacker-controlled QoS fields (interval, framing, phy, sdu, rtn, latency, pd) through the stream->qos pointer with only a stream != NULL guard. stream->qos is NULL for any stream that has been codec-configured via bt_bap_stream_config() but not yet added to a unicast group (it is set only by unicast_group_add_stream()).
A malicious or buggy remote ASCS server, to which the local device is connected as a BAP unicast client, can send a GATT notification announcing the ASE has entered the QoS Configured state while the local endpoint is still in the Codec Configured state — a transition the dispatcher explicitly permits — during that window, causing a write through a NULL pointer and a crash (denial of service). The data written is itself remote-controlled.
The defect shipped in v4.3.0 and v4.4.0 (and earlier). The fix re-points all BAP QoS storage to the always-valid embedded ep->qos struct, eliminating the NULL dereference.
Weakness: CWE-476
Which versions are affected by CVE-2026-10593?
It affects 1 product.
Products include Zephyrproject Zephyr.
How do I fix CVE-2026-10593?
No fix has been published for CVE-2026-10593 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-10593 being exploited?
There is no known exploitation of CVE-2026-10593 in the wild and no public exploit code.
Other vulnerabilities in Zephyrproject Zephyr
- CVE-2026-5067 Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key
- CVE-2022-3806 Bluetooth HCI Error Handling Double Free
- CVE-2017-14199 Memory corruption in getaddrinfo
- CVE-2018-1000800 Null dereference in n/a
- CVE-2021-3329 DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer
Sources
Also known as GHSA-22q8-m94g-2pwh.