← Back

Zephyr

zephyr

Vendor: Zephyrproject • 163 CVEs

CVEs (163)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Zephyrproject
1Zephyr
Jun 17, 2026
Feb 18, 2024
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Unchecked length coming from user input in settings shell
1Zephyrproject
1Zephyr
Jun 17, 2026
Nov 21, 2023
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Possible variant of CVE-2021-3434 in function le_ecred_reconf_req.
1Zephyrproject
1Zephyr
Jun 17, 2026
Nov 21, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
An malicious BLE device can cause buffer overflow by sending malformed advertising packet BLE device using Zephyr OS, leading to DoS or potential RCE on the victim BLE device.
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 26, 2023
N/A· v4
7.8 HIGH· v3
N/A· v2
Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 25, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 13, 2023
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Unchecked user input length in /subsys/net/l2/wifi/wifi_shell.c can cause buffer overflows.
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 13, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Potential buffer overflow vulnerability in the Zephyr IEEE 802.15.4 nRF 15.4 driver
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 13, 2023
N/A· v4
7.5 HIGH· v3
N/A· v2
The SJA1000 CAN controller driver backend automatically attempt to recover from a bus-off event when built with CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=y. This results in calling k_sleep() in IRQ context, causing a fatal except...Show more
The SJA1000 CAN controller driver backend automatically attempt to recover from a bus-off event when built with CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=y. This results in calling k_sleep() in IRQ context, causing a fatal exception.Show less
1Zephyrproject
1Zephyr
Jun 17, 2026
Oct 6, 2023
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem
1Zephyrproject
1Zephyr
Jun 17, 2026
Sep 27, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Two potential signed to unsigned conversion errors and buffer overflow vulnerabilities at the following locations in the Zephyr IPM drivers.
1Zephyrproject
1Zephyr
Jun 17, 2026
Sep 27, 2023
N/A· v4
9.6 CRITICAL· v3
N/A· v2
Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem.
1Zephyrproject
1Zephyr
Jun 17, 2026
Sep 27, 2023
N/A· v4
10.0 CRITICAL· v3
N/A· v2
Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system.
1Zephyrproject
1Zephyr
Jun 17, 2026
Sep 26, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Two potential buffer overflow vulnerabilities at the following locations in the Zephyr eS-WiFi driver source code.
1Zephyrproject
1Zephyr
Jun 17, 2026
Sep 25, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
In Bluetooth mesh implementation If provisionee has a public key that is sent OOB then during provisioning it can be sent back and will be accepted by provisionee.
1Zephyrproject
1Zephyr
Jun 17, 2026
Aug 12, 2023
N/A· v4
6.8 MEDIUM· v3
N/A· v2
Potential buffer overflow vulnerabilities in the following locations: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_posix.c#L359 https://github.com/zephyrproject-rtos/zephyr/blo...Show more
Potential buffer overflow vulnerabilities in the following locations: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_posix.c#L359 https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_posix.c#L359 https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/usb/device/class/netusb/function_rndis... https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/usb/device/class/netusb/function_rndis.c#L841Show less
1Zephyrproject
1Zephyr
Jun 17, 2026
Jul 10, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host.
1Zephyrproject
1Zephyr
Jun 17, 2026
Jul 10, 2023
N/A· v4
8.0 HIGH· v3
N/A· v2
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, lead...Show more
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 potential RCE on the Host layer.Show less
1Zephyrproject
1Zephyr
Jun 17, 2026
Jul 10, 2023
N/A· v4
8.0 HIGH· v3
N/A· v2
The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer,...Show more
The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer, leading to a crash (DoS) or potential RCE on the Host layer. Show less
1Zephyrproject
1Zephyr
Jun 17, 2026
Jul 10, 2023
N/A· v4
7.5 HIGH· v3
N/A· v2
A missing nullptr-check in handle_ra_input can cause a nullptr-deref.
1Zephyrproject
1Zephyr
Jun 17, 2026
May 30, 2023
N/A· v4
7.7 HIGH· v3
N/A· v2
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.