Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
It was added in 52d34955e7 to our code, but never used in C code. It was introduced to upstream by https://github.com/bitcoin-core/secp256k1/pull/366/changes/001f1763c76c2f5599cdb8713692c618191226fe
[no changelog]
88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit removes an unused compiler flag from the build system for the older Trezor firmware. The flag was defined but never referenced anywhere in the source code, so removing it has no functional or security effect.
build(core+legacy+crypto): remove unused `ENABLE_MODULE_GENERATOR` flag
It is part of the https://github.com/BlockstreamResearch/secp256k1-zkp fork (added in 52d34955e7). After we moved to https://github.com/bitcoin-core/secp256k1 (in 67f3af619a) it's no longer used.
[no changelog]
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit removes an unused compiler flag called ENABLE_MODULE_GENERATOR from three build files. The flag was left over from an older version of a cryptographic library and no longer has any effect after Trezor switched to a different library version. There is no functional code change and no security risk.
build(core+legacy+crypto): remove deprecated `ECMULT_GEN_PREC_BITS` flag
It has been removed in https://github.com/bitcoin-core/secp256k1/pull/1058 and released in https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#050---2024-05-06.
[no changelog]
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 18/100
This commit removes an obsolete compiler flag called ECMULT_GEN_PREC_BITS from the build scripts for Trezor's cryptographic code. The upstream secp256k1 library deleted this flag in version 0.5.0, so Trezor is simply cleaning up its build configuration to match. There is no indication this change fixes an active security vulnerability; it is routine build maintenance.
Security candidatedocs(core): changelog for bootloader 2.1.18by obrusvit · 621d7978 · Oct 29, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
docs(core): changelog for bootloader 2.1.18
[no changelog]
(cherry picked from commit e2b710f84783630ab790993cd9078ec5ee1d3c7c)
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit is purely a documentation update. It moves a bootloader user-interface change note from a pending changelog fragment into the official bootloader changelog for version 2.1.18. There are no code changes and no security implications.
Security candidatedocs(legacy): changelog for 1.14.3by obrusvit · ebcec1b8 · Oct 29, 2026 · 4 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
docs(legacy): changelog for 1.14.3
[no changelog]
(cherry picked from commit a6c65360a4c328c4fcc75294cfec46132e8b1eb7)
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is purely a documentation update: it moves three changelog entries from draft files into the official CHANGELOG.md for the Trezor legacy firmware version 1.14.3. No code, firmware logic, or security behavior is changed. The listed security items describe changes that were already made in earlier commits and are only being summarized here.
AI review queueddocs(core): changelog for 2.13.1by obrusvit · 75c19c8c · Oct 29, 2026 · 18 filesMessage 72 · AdequateModerate 62Details
Commit message · obrusvit
docs(core): changelog for 2.13.1
[no changelog]
(cherry picked from commit 1c8e894ca5f88fa9789be04eef82f3453af57fc5)
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 62/100
This commit is a documentation-only changelog update for the Trezor firmware 2.13.1 release. It does not change any executable code, but it lists several security fixes that were included in this release: Solana transaction handling improvements, a fix for Unicode characters displaying incorrectly, and warnings for risky xpub exports. Because the commit itself only edits changelog files, the actual security fixes happened in earlier commits that are referenced but not shown here.
Security candidatetest(python): add generation of test attestation certificatesby M1nd3r · a135aa85 · Oct 29, 2026 · 8 filesMessage 87 · StrongInformational 15Details
Commit message · M1nd3r
test(python): add generation of test attestation certificates
- Also, generate test certificates for existing models.
[no changelog]
87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 15/100
This commit only adds test infrastructure: a script that generates fake attestation certificates for Trezor emulators and copies them into a test directory. The certificates use publicly documented hardcoded debug keys and are used by automated tests. There is no change to production firmware, real device security, or user-facing behavior.
Security candidatefix(core): make CLI autocomplete order-independentby tychovrahe · a87f044c · Oct 29, 2026 · 1 fileMessage 85 · StrongInformational 21Details
Commit message · tychovrahe
fix(core): make CLI autocomplete order-independent
- cli_autocomplete() used '\0' both as "no match yet" and as "this command ends here", so whether Tab stopped at a full name such as "reboot" or ran on to "reboot-to-bootloader" depended on the order of the command array. - Track the first match separately. Seen in the emulator, whose constructor registration keeps source order; on hardware GCC emits the section in reverse, which happened to hide it.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trust
AI analysis · Informational 21/100
This is a minor bug fix in the command-line interface (CLI) autocomplete feature used inside Trezor devices. When a user typed a partial command like 'reboot' and pressed Tab, the autocomplete behavior could differ depending on the internal order of the command list. In some builds (real hardware) it happened to work; in others (emulator) it could skip past a complete command name and suggest a longer one instead. The fix separates two meanings of the special '\0' character so autocomplete behaves consistently regardless of command order. There is no direct evidence this is a security vulnerability.
AI review queuedfix(core/caesar): make CS prompt fit on 1 screenby obrusvit · 0a400887 · Oct 28, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
fix(core/caesar): make CS prompt fit on 1 screen
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit removes a stray line-break from a Czech translation string so that a 'new wallet created' message fits on a single screen of the Trezor Safe 3 (Caesar) device. It is a cosmetic UI/layout fix with no security relevance.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Informational 15/100
This commit adds extra diagnostic commands to a hardware CI test script. It collects more information about USB ports and PCI devices when a Trezor hardware test fails, to help engineers debug permission or connectivity issues. There is no change to the firmware, wallet logic, cryptography, or any user-facing security behavior.
AI review queuedfix(tools): make changelog.py ignore dirsby M1nd3r · dba808db · Oct 27, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r
fix(tools): make changelog.py ignore dirs
- Previously, having a subdir in one of `.changelog.d/` made the `changelog_check` crash.
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100
This is a minor developer tooling fix. The changelog-checking script previously crashed if someone accidentally created a subdirectory inside a hidden changelog folder. The patch simply skips directories and only looks at files. It has no security relevance for users of the Trezor device or wallet software.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 43/100
This commit tightens how the Trezor Python library checks whether a connected hardware wallet is genuine. It adds stricter rules: certificates must now include a device model name, revoked and allowed keys cannot be mixed, signature types must match the chip that produced them, and older firmware that lacks new MCU-style proof support is rejected with a clear error. These are defensive hardening changes rather than a fix for a known active attack.
AI review queuedfix(translations): fix failing tests in CS and updates to DE ES FR PTby Michal Kazda · 8f2a9bcc · Oct 27, 2026 · 6 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(translations): fix failing tests in CS and updates to DE ES FR PT [no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates translation text files for Czech, German, Spanish, French, and Portuguese. It fixes wording inconsistencies and updates a signature file that records which translation version is current. There is no code change and no security relevance.
Security candidatefix(core/caesar): use Marquee in HS notifby obrusvit · b3fb1bde · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 18Details
Commit message · obrusvit
fix(core/caesar): use Marquee in HS notif
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 18/100
This is a user-interface polish change for the Trezor hardware wallet's Caesar homescreen layout. It makes long notification messages scroll smoothly using a 'Marquee' component instead of being cut off or overlapping warning icons. There is no security-relevant behavior change; it is purely about how text is displayed on screen.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · e5d5b4a2 · Oct 27, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine synchronization of translated user-interface text strings from the Crowdin translation platform. It only changes wording in Czech, German, Spanish, French, Indonesian, and Portuguese translation files, plus the corresponding translation signature metadata. There is no code, logic, or security behavior change.
chore(python): add root debug keys for T3W1 authentication
[no changelog]
67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 18/100
This commit adds two extra public debug root keys (Ed25519 and ML-DSA-44) to the Python trezorlib library so it can authenticate the upcoming T3W1 hardware variant during development. Debug keys are already public, non-production trust anchors; adding more of them is a routine key-list update and does not by itself create a vulnerability.
Security candidaterefactor(python): use ML-DSA-44 OID from cryptographyby M1nd3r · 2f97f951 · Oct 27, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · M1nd3r
refactor(python): use ML-DSA-44 OID from cryptography
- `SignatureAlgorithmOID.ML_DSA_44` is available since cryptography v49.0.0, introduced in https://github.com/pyca/cryptography/pull/14884.
[no changelog]
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryauthentication path
AI analysis · Informational 15/100
This is a minor code cleanup in the Python Trezor library. It replaces a hard-coded identifier for the ML-DSA-44 signature algorithm with the official constant provided by the cryptography library. There is no security bug being fixed and no change in behavior for users.
Security candidatefix(core): flash F4 firmware parts to their own addressesby tychovrahe · 5718d0aa · Oct 27, 2026 · 5 filesMessage 85 · StrongModerate 57Details
Commit message · tychovrahe
fix(core): flash F4 firmware parts to their own addresses
- split the F4 firmware upload image into part 1 and part 2 when flashing or combining, part 2 belongs at FIRMWARE_P2_START - writing it in one piece put part 2 over the secret sector - fix the misleading split_pad_to comment
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Moderate 57/100
This commit fixes a bug in Trezor's internal firmware flashing tools. Previously, when flashing or combining firmware for STM32F4-based devices, the second half of the firmware image was written to the wrong flash address (0x08100000) and could overwrite the 'secret sector'—a protected area that holds sensitive device secrets. The fix splits the firmware image into two parts and writes part 2 to its correct address (0x08120000). The bug is in developer/flash tooling, not in the device firmware itself, so ordinary users are not directly affected unless they use these internal tools.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update pathauthentication path
AI analysis · Low 27/100
This commit fixes how long text is shown on Trezor Safe 3 and similar devices using the 'Bolt' user interface. Previously, long messages in confirmation dialogs could be cut off or not fully visible. Now these dialogs can paginate (split across multiple swipeable pages) so users can read the entire content before approving. The change is a UI/UX improvement rather than a direct exploit fix, but truncated security warnings could theoretically lead users to confirm something they did not fully see.
Security candidatefix(core/bolt): Marquee for PIN promptby obrusvit · 5b2b65d5 · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 20Details
Commit message · obrusvit
fix(core/bolt): Marquee for PIN prompt
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 20/100
This commit changes the PIN entry screen so that long prompt text scrolls smoothly like a marquee instead of being crammed or clipped. It is a user-interface polish fix with no apparent security relevance.
AI review queuedfix(translations): fix failing tests in PTBR and ESby Michal Kazda · efbedc41 · Oct 27, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(translations): fix failing tests in PTBR and ES [no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates Spanish and Portuguese translation files for the Trezor hardware wallet. It shortens a few on-screen phrases and splits one phrase into separate versions for different device models so that text fits on screen correctly. There is no security change here—this is purely a translation and layout fix for failing tests.
Security candidatefix(core): give USB EP0 receptions a full-packet bufferby tychovrahe · 0b9ac86f · Oct 27, 2026 · 7 filesMessage 85 · StrongHigh 77Details
Commit message · tychovrahe
fix(core): give USB EP0 receptions a full-packet buffer
- the OTG core accepts a full packet on EP0 OUT however short the armed length; the stack armed the status stage with a NULL buffer and VCP received class requests into an 8-byte one, so a host could make the HAL write through NULL or past the VCP buffer - receive all of them into a packet-sized buffer in the device handle
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · High 77/100
This commit fixes a USB memory-safety bug in Trezor hardware wallets. When the device expected no data during the final 'status' handshake of a USB control transfer, it told the USB hardware to write incoming bytes to address zero (NULL) or into an 8-byte command buffer. The USB hardware can actually deliver a full 64-byte packet regardless of what length was requested, so a malicious or misbehaving USB host could make the device write memory past the intended location or through the NULL pointer, causing a crash or potentially worse. The fix gives every such reception a dedicated 64-byte buffer inside the device handle.
feat(tests,clear_signing): update definition fixtures from dev
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100
This commit updates an internal helper script used to refresh test data for Ethereum 'clear signing' definitions. It adds an optional --dev mode so developers can fetch unsigned development definitions from an internal-only server and verify them with development keys. There is no change to the firmware that runs on customer devices, no change to production signature verification, and no disclosed security issue.
Security candidaterefactor(core): rename feature noise to noise_kk1by Martin Milata · 32d898c2 · Oct 26, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
refactor(core): rename feature noise to noise_kk1
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit is a simple internal rename of a Rust build feature from 'noise' to 'noise_kk1' and removes one unused source file ('noise_xxpsk3.c') from the build. There is no change to how the device works, no bug fix, and no security-relevant behavior change visible in the diff.
Security candidatefix(core/bootloader): initialize BLE once on the wipe path [no changelog]by tychovrahe · e59fe6ac · Oct 26, 2026 · 2 filesMessage 85 · StrongInformational 18Details
Commit message · tychovrahe
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>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 18/100
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.