lowRISC / lowRISC/opentitan

[rom] What to do if reset reason is wrong?

Open
#7,974 21 comments 0 reactions 1 assignee Assigned to @cfrantz View on GitHub
Component:Security Earlgrey-PROD Candidate SW:ROM Type:FutureRelease
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

This came up through the security consultants.

Right now, Mask ROM probably performs its early function based on what reset reason it thinks it sees.
However, what if the reset reason itself is vulnerable to attacks, could this direct ROM to keep information that it should have erased?

For example, what should have been "POR" or "Security escalation" were changed to "warm boot" or "debug requested reset".

What would be the right thing to do here?
The hardware side can make this harder and use multiple bits per indication, but I think it would also make sense for software to treat it like POR if it can't make sense of the read back.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.