AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 41 Bitcoin

fix(core): lower maximum auto-lock delay to 149 hours

Public commit record

What the developer wrote

Authored by Ondřej Vejpustek

97/100 · Strong
fix(core): lower maximum auto-lock delay to 149 hours

Setting the auto-lock delay to the maximum crashed the firmware on
every boot. The old maximum of `0x2000_0000` ms is exactly half the
MicroPython tick period on 32-bit MCUs, which is the smallest delta
that `utime.ticks_add()` rejects with `OverflowError`.

A device that already stores the old maximum recovers after the update,
because `get_autolock_delay_ms()` clamps the stored value. The stored
value itself is not rewritten.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This update fixes a bug in Trezor hardware wallets where setting the screen auto-lock delay to its maximum value caused the device to crash every time it restarted. The old maximum was chosen so that it hit a limit inside the device's timekeeping code, triggering an overflow error. The fix lowers the maximum allowed auto-lock delay to 149 hours and adds a safety check so the device cannot accept a value that would cause the crash. A device already stuck with the old maximum will recover after updating because the firmware clamps the stored value down to a safe range.

Recommended action

Apply the firmware update. Users who previously set the auto-lock delay to the old maximum should update; the device will recover automatically. No further user action is required.

Security signals we found

01

Denial-of-service via configuration: setting a legitimate setting to its maximum value caused a persistent boot crash

02

Integer/overflow boundary issue in MicroPython ticks_add()

03

Missing input validation on user-configurable auto-lock delay

04

Recovery path exists after update because stored value is clamped at read time

Risk score

Why this scored 41/100

Our methodology →
Potential impact 12/30
Exploitability 0/25
Stealth signal 5/15
Affected reach 10/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.