diff options
author | Andrea Arcangeli <andrea@cpushare.com> | 2005-09-09 13:01:51 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-09-09 13:57:30 -0700 |
commit | 4c7fc7220f6a3cce9b3f4bd66362176df67df577 (patch) | |
tree | 5824a334335dcc283a76ffad6294ed0904364157 /lib | |
parent | 4d666d7ada2e14d71d463c85b8b5ef2e2e6723f2 (diff) | |
download | linux-stable-4c7fc7220f6a3cce9b3f4bd66362176df67df577.tar.gz linux-stable-4c7fc7220f6a3cce9b3f4bd66362176df67df577.tar.bz2 linux-stable-4c7fc7220f6a3cce9b3f4bd66362176df67df577.zip |
[PATCH] i386: seccomp fix for auditing/ptrace
This is the same issue as ppc64 before, when returning to userland we
shouldn't re-compute the seccomp check or the task could be killed during
sigreturn when orig_eax is overwritten by the sigreturn syscall. This was
found by Roland.
This was harmless from a security standpoint, but some i686 users reported
failures with auditing enabled system wide (some distro surprisingly makes
it the default) and I reproduced it too by keeping the whole workload under
strace -f.
Patch is tested and works for me under strace -f.
nobody@athlon:~/cpushare> strace -o /tmp/o -f python seccomp_test.py
make: Nothing to be done for `seccomp_test'.
Starting computing some malicious bytecode
init
load
start
stop
receive_data failure
kill
exit_code 0 signal 9
The malicious bytecode has been killed successfully by seccomp
Starting computing some safe bytecode
init
load
start
stop
174 counts
kill
exit_code 0 signal 0
The seccomp_test.py completed successfully, thank you for testing.
(akpm: collaterally cleaned up a bit of do_syscall_trace() too)
Signed-off-by: Andrea Arcangeli <andrea@cpushare.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions