Physical memory map
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Currently, LiteBox (VTL1) only knows its physical memory range. This can be a problem if it attempts to access physical memory addresses that VTL1 is not allowed to access (e.g., memory areas for UEFI, SMM, hypervisor, ...). Malicious VTL0 kernel or userspace processes might be able to trigger this condition. To avoid this problem, VTL0 should provide physical memory map to VTL1.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the VTL0/VTL1 boundary and the existing physical-memory range handling. Determine how VTL0 can expose an allowed physical memory map to VTL1 and identify the relevant tests or validation points; done means VTL1 uses the provided map and cannot access excluded regions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100