CVE-2026-5589

12th percentile - higher than 12% of all known CVEs

An integer underflow in bt_mesh_sol_recv() in the Bluetooth Mesh solicitation handling leads to an out-of-bounds write. When CONFIG_BT_MESH_OD_PRIV_PROXY_SRV is enabled, the function parses solicitation PDUs from raw BLE advertising payloads. The AD parsing loop reads an attacker-controlled length byte and computes reported_len - 3 without checking that reported_len >= 3. When reported_len is less than 3, the subtraction yields a negative value that bypasses the length guard and is then implicitly converted to a very large size_t when passed to net_buf_simple_pull_mem(). In builds without assertions, this wraps the buffer length and advances the data pointer far out of bounds, so subsequent reads dereference invalid memory. A nearby BLE device can trigger this with a non-connectable advertisement carrying a UUID16 AD structure and a crafted length byte, with no pairing or prior association required, potentially leading to denial of service or arbitrary code execution.

An attacker within Bluetooth range can crash the system or gain control without any authentication, posing a serious threat to devices using the Zephyr Bluetooth Mesh stack.

It is recommended to apply patches provided by the Bluetooth Mesh stack vendor (e.g., Zephyr) and enable assertions in production builds if feasible.