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

fix(core): don't send `ButtonRequest` after unpairing

Public commit record

What the developer wrote

Authored by Roman Zeyde

89/100 · Strong
fix(core): don't send `ButtonRequest` after unpairing

Otherwise, it will fail since BLE is disconnected.

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This is a small bug fix in the Trezor hardware wallet firmware. After a user unpairs a Bluetooth device, the device was trying to send a button-press request over the now-disconnected Bluetooth link, which would fail. The fix stops sending that request during the success screen shown right after unpairing. It is a robustness fix, not a security vulnerability fix.

Recommended action

No immediate security action required. Treat as a normal firmware robustness improvement. If auditing, verify that no other post-disconnection flows emit ButtonRequest on a stale transport.

Security signals we found

01

Bluetooth disconnection state mishandled

02

UI flow emits message on disconnected transport

03

No changelog entry provided

Risk score

Why this scored 19/100

Our methodology →
Potential impact 3/30
Exploitability 2/25
Stealth signal 2/15
Affected reach 2/15
Confidence 7/10
Evidence quality 3/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.