CVE-2026-10774: dos in zephyrproject zephyr
Zephyr's Bluetooth Mesh subnet key management leaks one PSA Crypto key slot on every subnet-key teardown. In subsys/bluetooth/mesh/subnet.c, net_keys_create() imports the Private Beacon Key into a PSA key slot under CONFIG_BT_MESH_PRIV_BEACONS (enabled by default), but subnet_keys_destroy() guarded the matching psa_destroy_key() with CONFIG_BT_MESH_V1d1. That Kconfig symbol was removed when explicit Mesh 1.0.1 support was dropped, so the destroy branch became permanently dead code and the import is never balanced by a destroy. The imbalanced teardown is reached every time subnet keys are destroyed: deleting a subnet (Config Server NetKey Delete), completing a Key Refresh Procedure (which retires the old key set), and resetting/re-provisioning the node. The over-the-air triggers are processed only under the node's device key, so they are exercisable by the provisioner or network administrator that owns the node, reachable over the Bluetooth Mesh network. With the default CONFIG_MBEDTLS_PSA_KEY_SLOT_COUNT of 16, repeated add/delete or key-refresh cycles exhaust the shared PSA key-slot pool after roughly a dozen rounds. Once exhausted, bt_mesh_private_beacon_key() and thus subnet creation fail: the node can no longer add subnets or complete key refresh, and other PSA crypto consumers on the device may be starved, until the device is rebooted. The fix aligns the destroy guard with the import guard (CONFIG_BT_MESH_PRIV_BEACONS) so each slot is freed.
AI Analysis
Technical Summary
Zephyr's Bluetooth Mesh subsystem leaks one PSA Crypto key slot each time a subnet key is torn down because the code importing the Private Beacon Key into a PSA key slot is enabled by default (CONFIG_BT_MESH_PRIV_BEACONS), but the corresponding key destruction code is conditionally compiled under a removed configuration (CONFIG_BT_MESH_V1d1). As a result, the key slots are never freed. This imbalance occurs during subnet deletion, key refresh completion, or node reset/re-provisioning, all of which can be triggered over-the-air by authorized provisioners or network administrators. With the default PSA key slot count of 16, about a dozen such cycles exhaust the key slots, causing failures in subnet creation and key refresh operations and potentially starving other PSA crypto consumers until reboot. The fix involves aligning the destroy guard with the import guard to ensure proper freeing of key slots.
Potential Impact
The vulnerability causes a denial of service by exhausting PSA Crypto key slots on the device, which prevents the node from adding new subnets or completing key refresh procedures. This can also affect other PSA crypto consumers on the device. The impact is limited to availability and requires high privileges (provisioner or network administrator) to trigger. There is no confidentiality or integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix aligns the key destruction guard with the import guard to properly free PSA key slots. Until a patch is available, affected devices may require reboot to recover from key slot exhaustion. No generic mitigations are specified.
CVE-2026-10774: dos in zephyrproject zephyr
Description
Zephyr's Bluetooth Mesh subnet key management leaks one PSA Crypto key slot on every subnet-key teardown. In subsys/bluetooth/mesh/subnet.c, net_keys_create() imports the Private Beacon Key into a PSA key slot under CONFIG_BT_MESH_PRIV_BEACONS (enabled by default), but subnet_keys_destroy() guarded the matching psa_destroy_key() with CONFIG_BT_MESH_V1d1. That Kconfig symbol was removed when explicit Mesh 1.0.1 support was dropped, so the destroy branch became permanently dead code and the import is never balanced by a destroy. The imbalanced teardown is reached every time subnet keys are destroyed: deleting a subnet (Config Server NetKey Delete), completing a Key Refresh Procedure (which retires the old key set), and resetting/re-provisioning the node. The over-the-air triggers are processed only under the node's device key, so they are exercisable by the provisioner or network administrator that owns the node, reachable over the Bluetooth Mesh network. With the default CONFIG_MBEDTLS_PSA_KEY_SLOT_COUNT of 16, repeated add/delete or key-refresh cycles exhaust the shared PSA key-slot pool after roughly a dozen rounds. Once exhausted, bt_mesh_private_beacon_key() and thus subnet creation fail: the node can no longer add subnets or complete key refresh, and other PSA crypto consumers on the device may be starved, until the device is rebooted. The fix aligns the destroy guard with the import guard (CONFIG_BT_MESH_PRIV_BEACONS) so each slot is freed.
CVSS v3.1
Score 2.4low
Affected software
zephyrproject
zephyr
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Zephyr's Bluetooth Mesh subsystem leaks one PSA Crypto key slot each time a subnet key is torn down because the code importing the Private Beacon Key into a PSA key slot is enabled by default (CONFIG_BT_MESH_PRIV_BEACONS), but the corresponding key destruction code is conditionally compiled under a removed configuration (CONFIG_BT_MESH_V1d1). As a result, the key slots are never freed. This imbalance occurs during subnet deletion, key refresh completion, or node reset/re-provisioning, all of which can be triggered over-the-air by authorized provisioners or network administrators. With the default PSA key slot count of 16, about a dozen such cycles exhaust the key slots, causing failures in subnet creation and key refresh operations and potentially starving other PSA crypto consumers until reboot. The fix involves aligning the destroy guard with the import guard to ensure proper freeing of key slots.
Potential Impact
The vulnerability causes a denial of service by exhausting PSA Crypto key slots on the device, which prevents the node from adding new subnets or completing key refresh procedures. This can also affect other PSA crypto consumers on the device. The impact is limited to availability and requires high privileges (provisioner or network administrator) to trigger. There is no confidentiality or integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix aligns the key destruction guard with the import guard to properly free PSA key slots. Until a patch is available, affected devices may require reboot to recover from key slot exhaustion. No generic mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-03T15:44:07.840Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6f58c1bf32cb7a34aa3d61
Added to database: 08/02/2026, 14:48:33 UTC
Last enriched: 08/10/2026, 15:17:32 UTC
Last updated: 09/16/2026, 10:01:30 UTC
Views: 76
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.