From d3597c7f18e75f141addd78a4f7ab4e8a177cfb3 Mon Sep 17 00:00:00 2001
From: Stephen Miller <56742918+StevenMiller123@users.noreply.github.com>
Date: Sat, 9 May 2026 18:09:51 -0500
Subject: [PATCH] Kernel.Vmm: Fix protection check for file mappings (#4388)

---
 src/core/memory.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/core/memory.cpp b/src/core/memory.cpp
index 0335df6f6..64b1bb750 100644
--- a/src/core/memory.cpp
+++ b/src/core/memory.cpp
@@ -702,7 +702,7 @@ s32 MemoryManager::MapFile(void** out_addr, VAddr virtual_addr, u64 size, Memory
 
     handle = file->f.GetFileMapping();
 
-    if (False(file->f.GetAccessMode() & Common::FS::FileAccessMode::Write) ||
+    if (False(file->f.GetAccessMode() & Common::FS::FileAccessMode::Write) &&
         False(file->f.GetAccessMode() & Common::FS::FileAccessMode::Append)) {
         // If the file does not have write access, ensure prot does not contain write
         // permissions. On real hardware, these mappings succeed, but the memory cannot be