[0.4.14][NTOSKRNL] Workaround CORE-16387 & CORE-16449

Both was introduced by activating feature
MiWriteProtectSystemImage() once.
Imho this feature is not stable yet, therefore I disable
it for releases.

Both problems most likely got visible by 0.4.12-dev-386-g
65dbfc2868

Master remains affected for now.
How long shall I recurrently workaround this?
Someone needs to dig into why that feature on ros
does not work similar to the Windows implementation yet.

Worked around like I did for all releases since 0.4.13 already.
This commit is contained in:
Joachim Henze 2020-08-15 16:27:12 +02:00
parent 22210acfdf
commit 6302156cb1

View file

@ -44,7 +44,7 @@ PVOID MmUnloadedDrivers;
PVOID MmLastUnloadedDrivers;
BOOLEAN MmMakeLowMemory;
BOOLEAN MmEnforceWriteProtection = TRUE;
BOOLEAN MmEnforceWriteProtection = FALSE; // FIXME: should be TRUE, but that would cause CORE-16387 & CORE-16449
PMMPTE MiKernelResourceStartPte, MiKernelResourceEndPte;
ULONG_PTR ExPoolCodeStart, ExPoolCodeEnd, MmPoolCodeStart, MmPoolCodeEnd;