In my reply to FD-post "GNU libc/regcomp(3) Multiple Vulnerabilities" I indicated, that I found and reported the same bug while searching for resource starvation bugs two years ago. So I dug out the programs from back than to test suid binaries on recent linux distro and kernel. While it is still possible to trigger quite a few different flaws, none of them is quite interesting enough to investigate (mostly NULL and -1 derefs). But I got a minor but funny fault: When executing a process as normal user, one can open /proc/[pid]/ entries and keep them open, even after executing a suid binary. Thus it is possible e.g. to * Find stack base even with stack randomization * Modify oom_adj and kill the suid-binary with SIGKILL * Modify the coredump filter * Read limits Damn it, that /proc/self/mem is not rw See http://www.halfdog.net/Security/2011/SuidBinariesAndProcInterface/ Apart from that, ping6 contains a trivial buffer overflow using the size parameter (>128000), but I think it is not exploitable to gain root privileges. See http://www.halfdog.net/Security/2011/Ping6BufferOverflow/