Why it a security risk to execute system calls on user stack


Problem

When a process invokes a system call, it executes on its kernel stack instead of its user stack.

1. Why would it be a security risk to execute system calls on the user stack?

2. The amount of memory allocated for the kernel stack of each process is only a couple of pages (e.g., 8192 bytes). How do we know execution of the system call will not overflow the kernel stack?

Request for Solution File

Ask an Expert for Answer!!
Data Structure & Algorithms: Why it a security risk to execute system calls on user stack
Reference No:- TGS03256731

Expected delivery within 24 Hours