|author||Rich Felker <firstname.lastname@example.org>||2012-10-15 11:42:46 -0400|
|committer||Rich Felker <email@example.com>||2012-10-15 11:42:46 -0400|
block uid/gid changes during posix_spawn
usage of vfork creates a situation where a process of lower privilege may momentarily have write access to the memory of a process of higher privilege. consider the case of a multi-threaded suid program which is calling posix_spawn in one thread while another thread drops the elevated privileges then runs untrusted (relative to the elevated privilege) code as the original invoking user. this untrusted code can then potentially modify the data the child process will use before calling exec, for example changing the pathname or arguments that will be passed to exec. note that if vfork is implemented as fork, the lock will not be held until the child execs, but since memory is not shared it does not matter.
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions