fix(core/bootloader): honour refresh_index in DebugLinkRecordScreen [no changelog]
What changed, and why it matters
This is a tiny bug fix in the Trezor bootloader's testing/debugging helper. A screen-recording feature used only during automated emulator tests was ignoring a 'refresh index' number, so multiple recordings taken after emulator restarts would overwrite each other. The change makes the code use the provided index. It is not a security vulnerability affecting real devices or users.
No security action needed. Treat as normal test-infrastructure bug fix.
Security signals we found
No security-relevant signal: change is in a debug/test-only code path
No input validation, memory safety, or cryptographic changes
No privilege boundary crossed
Evidence from the diff
In the bootloader’s DebugLinkRecordScreen handler, display_record_start() was hardcoded with refresh_index=0. The patch passes msg.refresh_index when present. This only affects the debuglink test harness (emulator screen recording) and has no production security implications.
Changed components
core/embed/projects/bootloader/workflow/debuglink.cDebugLinkRecordScreen handlerbootloader emulator test toolingInspect captured patch +2 / −1
### core/embed/projects/bootloader/workflow/debuglink.c
@@ -148,7 +148,8 @@ static debuglink_result_t debuglink_process_record_screen(protob_io_t *io) {
size_t dir_len = strnlen(buffer, sizeof(buffer));
if (dir_len > 0) {
- display_record_start((uint8_t *)buffer, dir_len, 0);
+ display_record_start((uint8_t *)buffer, dir_len,
+ msg.has_refresh_index ? msg.refresh_index : 0);
res = DEBUGLINK_RESULT_REPAINT;
} else {
display_record_stop();Why this scored 20/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.