PT-2026-65865 · Zephyrproject · Zephyr
CVE-2026-10684
·
Published
2026-07-29
·
Updated
2026-07-29
CVSS v3.1
3.0
Low
| Vector | AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:L |
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.
Fix
Out of bounds Read
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Zephyr