chore(vendor): update libtropic to v3.2.1
What changed, and why it matters
This commit updates a bundled third-party library called libtropic from version 3.1.0 to version 3.2.1 inside the Trezor firmware repository. The actual code changes are not visible because only a submodule pointer was changed (one line modified in the vendor/libtropic path). There is no information in the commit itself saying this fixes a security problem, and no independent references were provided. On its own, this looks like a routine maintenance update.
Review the libtropic v3.2.1 release notes and the diff between v3.1.0 and v3.2.1 in the upstream libtropic repository to determine whether this update addresses any security issues. If Trezor publishes a security advisory or changelog entry for this firmware change, evaluate it separately.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit is a vendor submodule bump: vendor/libtropic is updated from v3.1.0 to v3.2.1. The diff is not available because GitHub submodule updates typically show only a pointer change (one commit hash replaced by another). Without the contents of the new libtropic version or a changelog, no specific vulnerability, attack surface, or security fix can be identified from this commit alone.
Changed components
vendor/libtropic submoduleInspect captured patch +1 / −1
Diff not available from the source API.Why this scored 2/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.