From 928625ccfa9f1bbbfaf83ffb4729d832cbe2f34f Mon Sep 17 00:00:00 2001 From: Joachim Henze Date: Tue, 17 Dec 2019 00:06:05 +0100 Subject: [PATCH] [0.4.13][NTOSKRNL] Workaround CORE-16387 & CORE-16449 Both most likely was introduced by activating feature MiWriteProtectSystemImage() once. Imho this feature is not stable yet, therefore I disable it for releases. Confirmation of reporters will have to be collected after the commit. Both problems most likely got visible by 0.4.12-dev-386-g 65dbfc286818e18095b7cc0c85f63cde6b3e629d Master remains affected for now. If no fix will appear during 0.4.14-dev'ing, then I will commit this to master as well in 3months. --- ntoskrnl/mm/ARM3/sysldr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ntoskrnl/mm/ARM3/sysldr.c b/ntoskrnl/mm/ARM3/sysldr.c index ab6e1165cc1..2eaf2680e8b 100644 --- a/ntoskrnl/mm/ARM3/sysldr.c +++ b/ntoskrnl/mm/ARM3/sysldr.c @@ -44,7 +44,7 @@ PVOID MmUnloadedDrivers; PVOID MmLastUnloadedDrivers; BOOLEAN MmMakeLowMemory; -BOOLEAN MmEnforceWriteProtection = TRUE; +BOOLEAN MmEnforceWriteProtection = FALSE; // FIXME: should be TRUE, but would cause CORE-16387 PMMPTE MiKernelResourceStartPte, MiKernelResourceEndPte; ULONG_PTR ExPoolCodeStart, ExPoolCodeEnd, MmPoolCodeStart, MmPoolCodeEnd;