fabi/Xenia-Canary
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Kernel] MmSetAddressProtect: Disable changing protection in executable range

Browse Source
This commit is contained in:
Gliniak
2024-08-18 10:29:18 +02:00
parent 365a220b74
commit 0ad1e3d585
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/xenia/kernel/xboxkrnl/xboxkrnl_memory.cc
View File

@@ -17,6 +17,7 @@
#include "xenia/kernel/xboxkrnl/xboxkrnl_memory.h" #include "xenia/kernel/xboxkrnl/xboxkrnl_memory.h"
#include "xenia/kernel/xboxkrnl/xboxkrnl_private.h" #include "xenia/kernel/xboxkrnl/xboxkrnl_private.h"
#include "xenia/xbox.h" #include "xenia/xbox.h"
DEFINE_bool( DEFINE_bool(
ignore_offset_for_ranged_allocations, false, ignore_offset_for_ranged_allocations, false,
"Allows to ignore 4k offset for physical allocations with provided range. " "Allows to ignore 4k offset for physical allocations with provided range. "
@@ -513,6 +514,14 @@ void MmSetAddressProtect_entry(lpvoid_t base_address, dword_t region_size,
uint32_t protect = FromXdkProtectFlags(protect_bits); uint32_t protect = FromXdkProtectFlags(protect_bits);
auto heap = kernel_memory()->LookupHeap(base_address); auto heap = kernel_memory()->LookupHeap(base_address);
// More research required: 544307D1 uses it with base_address in xex range,
// which causes write exception in long term. Probably console disables
// modification of xex range page protection for security reasons.
if (heap->heap_type() == HeapType::kGuestXex) {
return;
}
heap->Protect(base_address.guest_address(), region_size, protect); heap->Protect(base_address.guest_address(), region_size, protect);
} }
DECLARE_XBOXKRNL_EXPORT1(MmSetAddressProtect, kMemory, kImplemented); DECLARE_XBOXKRNL_EXPORT1(MmSetAddressProtect, kMemory, kImplemented);