Users can point the user stack where they like, for example in the middle of some device's memory mapped IO area. If the kernel used the user's stack, it would then crap all over the device. X86_64, i386, 680x0 and ARM architectures all switch the stack on transitions from user to kernel, and make it easy to switch to stack back again when going back to user space. AFAIK, all architectures capable of drawing a distinction between user and kernel space do this because user space needs access to its own stack, but would be able to escalate privilege if it could modify any kernel stack.
Escalation of privilege, denial or service, ...
Users can point the user stack where they like, for example in the middle of some device's memory mapped IO area. If the kernel used the user's stack, it would then crap all over the device. X86_64, i386, 680x0 and ARM architectures all switch the stack on transitions from user to kernel, and make it easy to switch to stack back again when going back to user space. AFAIK, all architectures capable of drawing a distinction between user and kernel space do this because user space needs access to its own stack, but would be able to escalate privilege if it could modify any kernel stack.