[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
65dbfc2868

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.
This commit is contained in:
Joachim Henze 2019-12-17 00:06:05 +01:00
parent aa2b39c872
commit 928625ccfa

View file

@ -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;