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

Fix potential buffer overflow in posix memory handling

Browse Source
This commit is contained in:
Herman S.
2025-10-08 11:41:02 +09:00
parent bc3585d0ef
commit 28e48410c5
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/xenia/base/memory_posix.cc
View File

@@ -184,7 +184,8 @@ bool QueryProtect(void* base_address, size_t& length, PageAccess& access_out) {
while (std::getline(memory_maps, maps_entry_string)) { while (std::getline(memory_maps, maps_entry_string)) {
std::stringstream entry_stream(maps_entry_string); std::stringstream entry_stream(maps_entry_string);
uintptr_t map_region_begin, map_region_end; uintptr_t map_region_begin, map_region_end;
char separator, protection[4]; char separator;
char protection[5]; // 4 chars (e.g., "r-xp") + null terminator
entry_stream >> std::hex >> map_region_begin >> separator >> entry_stream >> std::hex >> map_region_begin >> separator >>
map_region_end >> protection; map_region_end >> protection;
@@ -199,7 +200,7 @@ bool QueryProtect(void* base_address, size_t& length, PageAccess& access_out) {
while (std::getline(memory_maps, maps_entry_string)) { while (std::getline(memory_maps, maps_entry_string)) {
std::stringstream next_entry_stream(maps_entry_string); std::stringstream next_entry_stream(maps_entry_string);
uintptr_t next_map_region_begin, next_map_region_end; uintptr_t next_map_region_begin, next_map_region_end;
char next_protection[4]; char next_protection[5]; // 4 chars (e.g., "r-xp") + null terminator
next_entry_stream >> std::hex >> next_map_region_begin >> separator >> next_entry_stream >> std::hex >> next_map_region_begin >> separator >>
next_map_region_end >> next_protection; next_map_region_end >> next_protection;