Resource-exhaustion DoS via unreleased PSA key slots
Published Aug 2, 2026 · Updated Aug 2, 2026
Resource exhaustion in Zephyr RTOS 3.6.0 through 4.4.1 allows remote authenticated users to interrupt Bluetooth Mesh key management. subnet_keys_destroy() places the Private Beacon Key destroy call behind a removed Kconfig symbol, leaving every matching PSA key import unreleased. Under the default 16-slot pool, a device-key holder can exhaust slots after roughly a dozen teardown cycles, preventing subnet creation or key refresh until reboot.
Summary
What happened
Resource exhaustion in Zephyr RTOS 3.6.0 through 4.4.1 allows remote authenticated users to interrupt Bluetooth Mesh key management. subnet_keys_destroy() places the Private Beacon Key destroy call behind a removed Kconfig symbol, leaving every matching PSA key import unreleased. Under the default 16-slot pool, a device-key holder can exhaust slots after roughly a dozen teardown cycles, preventing subnet creation or key refresh until reboot.
The record
- CVE
- CVE-2026-10774
- Published
- Aug 2, 2026
- Updated
- Aug 2, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-401, T1499
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Aug 2, 2026CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.
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