Memory corruption via shared BLE reassembly buffer
Published Jul 11, 2026 · Updated Jul 11, 2026
Out-of-bounds write in Zephyr RTOS 3.6.0 through 4.4.0 allows physically proximate attackers to corrupt memory over BLE. The notify_handler function appends Broadcast Receive State notifications from multiple connections to one 512-byte file-static buffer without checking tailroom. Exploitation requires concurrent Scan Delegator connections and a sufficiently large ATT MTU, causing cross-connection data corruption, a crash, or memory corruption.
Summary
What happened
Out-of-bounds write in Zephyr RTOS 3.6.0 through 4.4.0 allows physically proximate attackers to corrupt memory over BLE. The notify_handler function appends Broadcast Receive State notifications from multiple connections to one 512-byte file-static buffer without checking tailroom. Exploitation requires concurrent Scan Delegator connections and a sufficiently large ATT MTU, causing cross-connection data corruption, a crash, or memory corruption.
The record
- CVE
- CVE-2026-10660
- Published
- Jul 11, 2026
- Updated
- Jul 11, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-787, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2026CVE publishedPublication date reported by the CVE source.
- Jul 11, 2026Record 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.
- Affected versionversion=3.6.0 <4.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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