Dan Carpenter b530fb69cf isdn: strcpy() => strlcpy() ... setup.phone and setup.eazmsn are 32 character buffers. rcvmsg.msg_data.byte_array is a 48 character buffer. sc_adapter[card]->channel[rcvmsg.phy_link_no - 1].dn is 50 chars. The rcvmsg struct comes from the memcpy_fromio() in receivemessage(). I guess that means it's data off the wire. I'm not very familiar with this code but I don't see any reason to assume these strings are NULL terminated. Also it's weird that "dn" in a 50 character buffer but we only seem to use 32 characters. In drivers/isdn/sc/scioc.h, "dn" is only a 49 character buffer. So potentially there is still an issue there. The important thing for now is to prevent the memory corruption. Signed-off-by: Dan Carpenter <error27@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2010-10-08 10:21:22 -07:00
..
card.h
command.c
event.c
hardware.h
includes.h
init.c	include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h	2010-03-30 22:02:32 +09:00
interrupt.c	isdn: strcpy() => strlcpy()	2010-10-08 10:21:22 -07:00
ioctl.c	isdn: fix information leak	2010-08-05 13:21:25 -07:00
Kconfig
Makefile
message.c
message.h
packet.c
scioc.h
shmem.c
timer.c