CVE-2026-10684

published 29 Jul 2026 · updated 31 Aug 2026

Out-of-bounds read in coredump shell when printing stored-dump target code

3.0LowCVSS 3.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.3.1 and 4.4.2.

In subsys/debug/coredump/coredump_shell.c, print_coredump_hdr() used the 16-bit tgt_code field of a stored Zephyr coredump header directly as an index into coredump_target_code2str[], a fixed 7-element array of string pointers, with no bounds check. A stored coredump whose tgt_code is >= 7 causes an out-of-bounds read of a char* up to ~64K entries past the array; that value is passed as the %s argument to shell_print, which dereferences and walks it as a string. The result is either disclosure of device memory contents to the shell user or a crash when the out-of-bounds pointer is unmapped. The defect is reached via the coredump print shell command (cmd_coredump_print_stored_dump -> pretty_print_coredump -> parse_and_print_coredump -> print_coredump_hdr). The tgt_code field is device-generated and in-range during normal crash handling, so triggering requires local shell access plus the ability to stage or corrupt the stored coredump in the flash/in-memory backend. Introduced in v4.2.0 (commit 13abd7fe730) and present through v4.4.0; fixed by clamping out-of-range codes to the 'unknown' (index 0) entry.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
zephyrproject>=4.2.0 <4.3.1, >=4.4.0 <4.4.24.3.1, 4.4.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-10684 severity on Zeptric[![CVE-2026-10684](https://zeptric.io/badge/cve/CVE-2026-10684.svg)](https://zeptric.io/cve/CVE-2026-10684)