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

usb: block HWW during U2F workflows

Public commit record

What the developer wrote

Authored by benma's agent

68/100 · Adequate
usb: block HWW during U2F workflows

Track detached U2F workflow lifetimes independently of their public
result state. Return HWW_RSP_BUSY before starting an HWW request while a
U2F workflow can still own the shared UI.

This prevents HWW session reset and cancellation paths from invalidating
live U2F UI objects. Add regressions for the lifetime guard and busy
response.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a concurrency bug in the BitBox02 hardware wallet's USB handling. When a U2F (two-factor authentication) workflow is still running on the device's screen, a new hardware wallet request could previously start and reset or cancel the U2F workflow, potentially corrupting its user-interface state. The fix makes new hardware wallet requests return 'busy' while any U2F workflow is active, and tracks U2F workflow lifetimes independently of their public result state.

Recommended action

Treat this as a security-hardening fix with denial-of-service and potential UI-state integrity implications. Review whether any other endpoints or reset paths can still preempt U2F workflows, and ensure the busy response is handled correctly by host software to avoid user confusion.

Security signals we found

01

Concurrency/lifetime bug between HWW and U2F USB endpoints

02

Use-after-free or invalidation risk for live U2F UI objects

03

Session reset/cancellation path could corrupt shared UI state

04

New busy-response guard prevents overlapping workflows

05

Regression tests added for both lifetime guard and busy response

Risk score

Why this scored 59/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 10/15
Confidence 7/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.