You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In StandaloneMmPkg when a binary is loaded it's code sections will be marked with the read-only memory protections. If this image then fails, it will be unloaded and its memory reclaimed. However, the core does not unset the read-only attribute and if that address is re-used later it will cause an access violation when attempting to write to the memory still marked as read-only.
Expected Behavior
The memory should be restored to the default RW so future allocations of that memory are consistent with other memory allocations.
Is there an existing issue for this?
Current Behavior
In StandaloneMmPkg when a binary is loaded it's code sections will be marked with the read-only memory protections. If this image then fails, it will be unloaded and its memory reclaimed. However, the core does not unset the read-only attribute and if that address is re-used later it will cause an access violation when attempting to write to the memory still marked as read-only.
Expected Behavior
The memory should be restored to the default RW so future allocations of that memory are consistent with other memory allocations.
Steps To Reproduce
Reproduction steps available internally.
Build Environment
Version Information
Urgency
High
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
The text was updated successfully, but these errors were encountered: