To further clarify my question, another way of asking it is: what is the internals of NtMapViewOfSection() - how does it modify the memory attributes at the page level? NtMapViewOfSection() is only applicable for userspace buffer right?

I would like to know of an equivalent to VirtualProtect() for kernelspace. Ie, given a virtual memory range returned from ExAllocatePool, or the current memory space occupied by the driver itself in memory, how do I set the memory read/write/execute attributes - the one ultimately ending up as modif...