Exposes MEM_FlushCache() via PROC_FlushMemory() and PROC_InvalidateMemory().
Exposes PROC_FlushMemory() and PROC_InvalidateMemory via PROCWRAP_FlushMemory()
PROCWRAP_InvalidateMemory() respectively, which then allows them to be called
without any argument checking from userspace.
This allows direct unchecked access to functions which can discard any kernel
data from userspace. Not only is this a security issue, but has no isolation
from buggy usage.
Why would userspace want to know about kernel addresses?