Re: Accessing Physical Memory & Other Process's Address Space

Thanks Charles...Let me rephrase my question and put it in the proper
context:
In 32 bit protected mode, each user process is allocated a 4GB address
space, whereby program data and code resides in lower 2GB and kernel
is mapped in the upper 2GB (in some cases it is 3GB for user and 1GB
for kernel). However the part of linear address space where kernel is
mapped, is not accessible to user process, due to the difference in
privilege levels. The question is that, do kernel mode processes also
get their address space mapped in the same manner. If yes, than it
implies that kernel is also mapped into a part of their address space.
If a kernel mode driver is malicious, it can easily make arbitrary
changes to kernel, as kernel is mapped to its address space and is
accessible also (as both are operating at the same privilege level).
Am I thinking on the correct lines or there is some misconception?

.