CVE-2026-12233
The PSA Protected Storage credential backend (subsys/net/lib/tls_credentials/tls_credentials_trusted.c) declared its credential-store mutex as a plain zero-filled static struct k_mutex credential_lock; and never called k_mutex_init() on it. A statically zero-filled k_mutex has an uninitialized wait queue (its dlist head/tail are NULL instead of the self-referential sentinels that k_mutex_init/K_MUTEX_DEFINE install). The uncontended lock path does not touch the wait queue, so the defect is latent and serialized use behaves correctly. When two execution contexts contend on the lock, k_mutex_lock() pends the blocking thread on the wait queue via z_pend_curr(), which calls sys_dlist_append() on the zeroed list and dereferences a NULL tail pointer (tail->next = node), faulting the kernel. The lock is held during TLS handshake credential loading and by all credential add/get/delete operations, so a deployment performing concurrent TLS handshakes (for example a server handling multiple simultaneous connections from a remote peer) or a credential-management operation concurrent with a handshake can trigger the dereference. The impact is a denial of service: a deterministic kernel panic / device reset on the first contention. There is no memory corruption beyond the NULL dereference and no confidentiality or integrity impact; mutual exclusion on the fast path remains correct. Exposure is limited to builds with CONFIG_TLS_CREDENTIALS_BACKEND_PROTECTED_STORAGE enabled (PSA Protected Storage / TF-M platforms); the default volatile RAM backend initializes its lock correctly and is unaffected. The fix initializes the mutex statically with K_MUTEX_DEFINE(credential_lock), providing a valid wait queue so the contended path no longer touches a NULL list.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.9
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS probability
- 0.31%
- CWE
- CWE-665
- Published
- 2026-08-12
- Last modified
- 2026-08-13
Affected products
- zephyrproject zephyr
Weakness type
Related vulnerabilities
- CVE-2026-87616 — Improper initialization in Views in Google Chrome on on Windows prior to 153.0.8010.36 allowed a...
- CVE-2026-78940 — Improper initialization in Network in Google Chrome prior to 152.0.7977.65 allowed a remote...
- CVE-2026-20734 — Improper initialization in some firmware for some Intel(R) Active Management Technology (Intel(R)...
- CVE-2026-44434 — Quicly is vulnerable to stateless reset injection
- CVE-2026-54777 — CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance
- CVE-2026-54409 — A malicious actor with access to the network and under certain conditions could exploit an Improper...
- CVE-2026-54279 — AIOHTTP: Host-Only Cookies Become Domain Cookies After CookieJar Persistence
- CVE-2026-12539 — Docker Sandboxes ICMP egress restriction bypass after daemon restart