CVE-2023-0397

Device crash via zero Bluetooth buffer count

Published Jan 19, 2023 · Updated Apr 3, 2025

Improper exceptional-condition handling in Zephyr RTOS 3.2 and earlier allows physically proximate attackers to crash devices. The le_read_buffer_size_complete function passes a controller-supplied zero le_max_num value to k_sem_init, leaving the ACL packet semaphore uninitialized before z_impl_k_sem_take dereferences its wait queue. Triggering requires a malicious or defective Bluetooth controller to return the invalid LE buffer count during initialization, interrupting the device through a null-pointer dereference.

CVSS severity9.6
Critical
EPSS probability0.47%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper exceptional-condition handling in Zephyr RTOS 3.2 and earlier allows physically proximate attackers to crash devices. The le_read_buffer_size_complete function passes a controller-supplied zero le_max_num value to k_sem_init, leaving the ACL packet semaphore uninitialized before z_impl_k_sem_take dereferences its wait queue. Triggering requires a malicious or defective Bluetooth controller to return the invalid LE buffer count during initialization, interrupting the device through a null-pointer dereference.

The record

CVE
CVE-2023-0397
Published
Jan 19, 2023
Updated
Apr 3, 2025
Vendor
Zephyr Project
Product
Zephyr RTOS
Classifications
CWE-703, CWE-665, T1499
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 19, 2023CVE publishedPublication date reported by the CVE source.
  2. Apr 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=unspecified <=v3.2

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Zephyr Project · Zephyr RTOSversion=unspecified <=v3.2

Published CVSS scores

9.6Zephyr Project CNACVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
6.0Zephyr Project GitHub Security AdvisoryCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-703Improper Check or Handling of Exceptional Conditions
CWE-665Improper Initialization
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo