Service interruption via unsolicited BLE response acceptance
Published Sep 19, 2025 · Updated Sep 19, 2025
Improper BLE response validation in Zephyr RTOS before 4.2.0 allows physically proximate attackers to interrupt service. The le_conn_rsp handler accepts an unsolicited response when its identifier matches, without verifying that the device sent a corresponding request. Unauthenticated BLE proximity is sufficient; the vendor reports protocol state confusion, memory corruption, and denial of service as consequences.
Summary
What happened
Improper BLE response validation in Zephyr RTOS before 4.2.0 allows physically proximate attackers to interrupt service. The le_conn_rsp handler accepts an unsolicited response when its identifier matches, without verifying that the device sent a corresponding request. Unauthenticated BLE proximity is sufficient; the vendor reports protocol state confusion, memory corruption, and denial of service as consequences.
The record
- CVE
- CVE-2025-10457
- Published
- Sep 19, 2025
- Updated
- Sep 19, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-358, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2025CVE publishedPublication date reported by the CVE source.
- Sep 19, 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.
- Affected versionversion=* <=4.1.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.
Weakness, pattern, technique
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