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

feat(core): Use ML-DSA-44 for MCU device attestation key.

Public commit record

What the developer wrote

Authored by Andrew Kozlik

62/100 · Adequate
feat(core): Use ML-DSA-44 for MCU device attestation key.

[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 swaps the cryptographic algorithm used for one of the Trezor hardware wallet's internal device-attestation keys from Ed25519 to ML-DSA-44, a post-quantum NIST-standardized signature scheme. It also enlarges the certificate storage area and doubles the production-test command-line input buffer. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a planned cryptographic modernization change.

Recommended action

Treat this as a high-risk cryptographic change rather than an active vulnerability. Review the integration of mldsa-native for constant-time properties, stack/heap usage, and side-channel behavior on the STM32U5 secure core. Verify that the new secret derivation path preserves the same security assumptions as the old curve25519-clamped derivation, and ensure certificate size limits and CLI buffer expansion do not introduce parsing or memory issues. Request a changelog entry and design documentation from the vendor.

Security signals we found

01

Algorithm migration from Ed25519 to ML-DSA-44 for device attestation

02

New third-party cryptographic submodule added (pq-code-package/mldsa-native)

03

Certificate storage size increased fourfold

04

CLI input buffer doubled, likely to handle larger signatures/keys

05

Secret key derivation path changed from curve25519 clamping to raw symmetric derivation

06

No changelog entry despite cryptographic change

Risk score

Why this scored 25/100

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