grsecurity forums

by **crashev** » Thu Aug 11, 2005 8:48 am

Hello,
I have really mass problem with Signal 11 on My box with grsecurity. Actually this problem occurs everywhere where I have grsecurity, its a lot of for example:
dmesg | grep signal

grsec: From XXX.124.26.XXX: signal 11 sent to /data/appp/http/index.pl[index.pl:3711] uid/euid:501/501 gid/egid:51/51, parent /usr/sbin/httpd.prefork[httpd.prefork:17363] uid/euid:501/501 gid/egid:51/5

or I can just run ./index.pl and also got
$ ./index.pl
<HTML>...
...
Segmentation fault (core dumped)

dmesg:
grsec: From XXX.XXX.16X.2X: signal 11 sent to /data/appp/http/index.pl[index.pl:5798] uid/euid:501/501 gid/egid:100/100, parent /bin/bash[bash:5783] uid/euid:501/501 gid/egid:100/100

More details on my system:
$ uname -a
Linux serwer 2.6.11.12-grsec #3 SMP Sat Jul 16 02:41:10 CEST 2005 i686 Intel(R)_XEON(TM)_CPU_1.80GHz unknown PLD Linux
RAM: 1GB

$ perl -v
This is perl, v5.8.7 built for i686-pld-linux-thread-multi

Thats what I got from core:
(gdb) bt
#0 0x4009e330 in Perl_pp_helem () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#1 0x400991b9 in Perl_runops_standard () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#2 0x4003b849 in S_call_body () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#3 0x4003b61c in Perl_call_sv () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#4 0x400aa2b0 in Perl_sv_clear () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#5 0x400aab30 in Perl_sv_free () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#6 0x400a250e in do_clean_objs () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#7 0x400a2494 in S_visit () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#8 0x400a2625 in Perl_sv_clean_objs () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#9 0x40039217 in perl_destruct () from /usr/lib/perl5/5.8.7/i686-pld-linux-thread-multi/CORE/libperl.so.5.8.0
#10 0x0804936a in main ()
(gdb)

Any clues whats goin on?
Regards.

by **tuxq** » Thu Aug 11, 2005 2:05 pm

It's not instability... it's grsec purposely killing it.

by **PaX Team** » Sun Aug 14, 2005 2:15 pm

crashev wrote:Hello,
I have really mass problem with Signal 11 on My box with grsecurity. Actually this problem occurs everywhere where I have grsecurity, its a lot of for example:
dmesg | grep signal

can you turn off randomization in PaX and see if the problem still manifests? i think there's a bug in there, would be nice if you could confirm it. if it helps, you could also selectively enable the various randomizations to see which one is the problematic one.

by **crashev** » Mon Aug 15, 2005 8:29 am

Actually I have PaX totally turned off and still got a lot of Signal 11 killing in dmesg.

by **tuxq** » Wed Aug 24, 2005 3:00 am

Are you using sysctl? If so, could you enable the options 1 by 1, after loading each, attempt to run the perl script? See which one of the options is causing it to do this.

grsecurity forums

grsecurity instability

grsecurity instability

Re: grsecurity instability