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

fix(core): remove rcc module from non-secure kernel

Public commit record

What the developer wrote

Authored by cepetr

62/100 · Adequate
fix(core): remove rcc module from non-secure kernel

[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 removes low-level clock-control code from the non-secure part of Trezor's STM32U5 firmware and replaces it with small, safe stubs. The stated reason is that the full clock-control peripheral (RCC) is not safely accessible when the kernel runs in non-secure mode, so using the vendor's standard routines there could cause problems. The change is defensive hardening rather than a clear, exploitable bug fix.

Recommended action

Treat as a hardening improvement. Review whether any remaining non-secure code still calls RCC registers directly, and verify that SystemCoreClock is reliably initialized before the non-secure kernel uses these stubs. No urgent user action is indicated by the diff alone.

Security signals we found

01

TrustZone/secure-monitor privilege boundary involved

02

Removal of peripheral access from less-privileged execution mode

03

Replacement of vendor HAL with constrained, mode-aware stubs

04

Defensive comment notes RCC is 'not fully accessible' in non-secure mode

Risk score

Why this scored 42/100

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