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

feat(nordic/ble): enable controlling TX power level from main MCU

Public commit record

What the developer wrote

Authored by tychovrahe

62/100 · Adequate
feat(nordic/ble): enable controlling TX power level from main MCU

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a feature that lets the main Trezor MCU tell the Bluetooth chip what radio transmit power to use. It is a normal feature addition and does not, by itself, look like a security vulnerability. The only notable risk is that if an attacker could already send malicious commands to the internal Bluetooth-to-main-MCU channel, they might be able to lower the Bluetooth signal strength, which could make the device harder to detect or more likely to disconnect unexpectedly. There is no evidence in the commit that such command injection is possible, and the commit does not claim to fix a security issue.

Recommended action

Treat as a feature commit, not a security patch. If reviewing for security, verify that the internal SPI/UART channel between the main MCU and Nordic BLE chip is authenticated and that only the main MCU can issue INTERNAL_CMD_SET_TX_POWER. Consider adding explicit bounds checking on the requested power level before calling ble_configure_tx_power(), even if the HCI layer currently clamps values, to make the code more robust against future controller changes.

Security signals we found

01

New internal command 0x10 added to BLE management interface

02

No explicit bounds validation on tx_power_level before HCI call

03

Relies on Zephyr HCI vendor command to enforce valid TX power levels

04

Default TX power set to +4 dBm

05

Status event now includes current power_level field

Risk score

Why this scored 17/100

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