-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent accessing RAM outside of the physical memory #160
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dehanj
reviewed
Mar 13, 2024
dehanj
force-pushed
the
match_qemu_ram_mem
branch
from
March 18, 2024 13:31
c6f4934
to
aa350a7
Compare
secworks
force-pushed
the
match_qemu_ram_mem
branch
from
March 18, 2024 14:12
4a827f2
to
ab8ca02
Compare
dehanj
force-pushed
the
match_qemu_ram_mem
branch
5 times, most recently
from
March 19, 2024 14:33
b974c8a
to
890b307
Compare
dehanj
changed the title
Match qemu ram mem
Prevent accessing RAM outside of the physical memory
Mar 20, 2024
Verified the function, not possible to address memory > |
dehanj
approved these changes
Mar 20, 2024
mchack-work
force-pushed
the
match_qemu_ram_mem
branch
from
March 20, 2024 13:22
890b307
to
08765ce
Compare
mchack-work
approved these changes
Mar 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed language nits in the docs for security_monitor. Looks good to me.
Signed-off-by: Joachim Strömbergson <[email protected]>
Signed-off-by: Joachim Strömbergson <[email protected]>
that the device must be reset to get out of trap. This change also breaks a critical path. Signed-off-by: Joachim Strömbergson <[email protected]>
Change name of cpu_monitor to security_monitor and increase its functionality to include RAM access violations. If addresses in RAM but outside of physical RAM is accessed in any way the security_monitor traps the CPU in the same way as it already did for execution violations.
Signed-off-by: Joachim Strömbergson <[email protected]>
mchack-work
force-pushed
the
match_qemu_ram_mem
branch
from
March 20, 2024 13:37
08765ce
to
29fd833
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an address filter to detect addresses to the RAM area that are lager than the current RAM memory (128 kByte). This makes the memory in a similar way to the RAM in QEMU.
Closes #158