Nix wrote:
On 17 Mar 2006, Arjan van de Ven wrote:
GCC emits a call to a __stack_chk_fail() function when the cookie is not
matching the expected value. Since this is a bad security issue; lets panic
the kernel
This turns even minor buffer overflows into complete denials of service.
only those who otherwise would get to the return address. So it turns a "own the machine" into a panic.
Not a "no side effects" thing....
If we're running in process context and the process is currently
killable it might make more sense to printk() a message and zap the
process; that way we only halt whatever service it is the attacker
hit us through.
maybe. The big question is if you can still trust the machine. That is highly questionable...
(and to kill the process you again need to trust bits of the stack, to get to current for example;
and you just found that the stack was compromised)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
