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

feat(core): introduce framebuffer_access applet privilege

Public commit record

What the developer wrote

Authored by cepetr

62/100 · Adequate
feat(core): introduce framebuffer_access applet privilege

[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 new security permission called framebuffer_access that controls whether a small helper app (applet) running on the Trezor can read from or write to the device's screen memory. Previously, applets could access the framebuffer based only on memory location checks. Now they must also be explicitly granted the framebuffer_access privilege. The change is a hardening/feature addition, not a fix for an active exploit, and it removes an older privilege called assets_area_access that was apparently unused or being replaced.

Recommended action

Treat as a security-hardening change. Review whether any existing applets besides coreapp legitimately need framebuffer access and ensure the privilege is granted only where required. Verify that mpu_update_region5 is invoked consistently whenever fb_access or active_fb state changes, and confirm the removed assets_area_access privilege was not relied upon elsewhere in the codebase.

Security signals we found

01

New capability-based privilege (framebuffer_access) added for applet framebuffer access

02

Syscall probes now gate framebuffer read/write on both privilege flag and MPU region membership

03

MPU region 5 configuration now depends on the new fb_access flag in APP/APP_SAES modes

04

Removal/replacement of the previous assets_area_access privilege field

05

coreapp explicitly granted framebuffer_access; third-party applets default to no framebuffer access

Risk score

Why this scored 46/100

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