Zephyrproject ≫ Zephyr

The bluetooth HCI host layer logic not clearing a global reference to a state pointer after handling connection events may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer, leading to a crash (DoS) or potent...

A missing nullptr-check in handle_ra_input can cause a nullptr-deref.

At the most basic level, an invalid pointer can be input that crashes the device, but with more knowledge of the device’s memory layout, further exploitation is possible.

Lack of proper validation in HCI Host stack initialization can cause a crash of the bluetooth stack

A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses.

Inconsistent handling of error cases in bluetooth hci may lead to a double free condition of a network buffer.

A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete.

usb device bluetooth class includes a buffer overflow related to implementation of net_buf_add_mem.

There is no check to see if slot 0 is being uploaded from the device to the host. When using encrypted images this means the unencrypted firmware can be retrieved easily.

There is an error in the condition of the last if-statement in the function smp_check_keys. It was rejecting current keys if all requirements were unmet.