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

fix(core/bootloader): initialize BLE once on the wipe path [no changelog]

Public commit record

What the developer wrote

Authored by tychovrahe

85/100 · Strong
fix(core/bootloader): initialize BLE once on the wipe path [no changelog]

drivers_init() already brought the driver up; the wipe branch called
ble_init() a second time. The STM32 driver ignores a repeated init, the
unix one re-registered its handles and failed, so a wipe boot command
ended on the failure screen in the emulator. Drop the second call and
give the unix driver the same already-initialized guard.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This is a small bug fix in the Trezor bootloader's wipe feature. When wiping the device, the code was accidentally initializing the Bluetooth (BLE) system twice. On real hardware the second call was ignored, but in the software emulator it caused the wipe process to end on an error screen. The patch removes the redundant second initialization and also makes the emulator's BLE driver ignore repeated initializations, matching the real hardware behavior. It does not appear to be a security vulnerability.

Recommended action

Treat as a routine functional fix. No security response required. Reviewers may verify that the unix BLE driver's initialized flag is correctly set and cleared elsewhere to prevent state inconsistency.

Security signals we found

01

No memory safety, authentication, cryptographic, or privilege-escalation issues visible in diff

02

Change is defensive hardening against double-initialization rather than an exploit path

03

Failure mode was a functional error screen in emulator, not a security bypass

04

No changelog entry suggests routine bug fix

Risk score

Why this scored 18/100

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