uvisor config isn`t under protected
- Dominant language
- C
- Stars
- 135
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
I found that the uvisor config was not under protected, the uvisor config was linked before the symbol __uvisor_secure_end, It`s different with the design.
```
// vmpu_arch_init_hw() in vmpu_armv7m.c
vmpu_mpu_set_static_acl(
0,
FLASH_ORIGIN,
((uint32_t) __uvisor_config.secure_end) - FLASH_ORIGIN,
UVISOR_TACLDEF_SECURE_CONST | UVISOR_TACL_EXECUTE,
0
);
```
Contributor guide
Research direction
Start in vmpu_armv7m.c at vmpu_mpu_set_static_acl and inspect how __uvisor_config is linked relative to __uvisor_secure_end. Compare the configured protected range with the stated design, then verify that the uvisor config is included under protection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100