David S. Miller 676d23690f net: Fix use after free by removing length arg from sk_data_ready callbacks. ... Several spots in the kernel perform a sequence like: skb_queue_tail(&sk->s_receive_queue, skb); sk->sk_data_ready(sk, skb->len); But at the moment we place the SKB onto the socket receive queue it can be consumed and freed up. So this skb->len access is potentially to freed up memory. Furthermore, the skb->len can be modified by the consumer so it is possible that the value isn't accurate. And finally, no actual implementation of this callback actually uses the length argument. And since nobody actually cared about it's value, lots of call sites pass arbitrary values in such as '0' and even '1'. So just remove the length argument from the callback, that way there is no confusion whatsoever and all of these use-after-free cases get fixed as a side effect. Based upon a patch by Eric Dumazet and his suggestion to audit this issue tree-wide. Signed-off-by: David S. Miller <davem@davemloft.net>		2014-04-11 16:15:36 -04:00
..
hci	NFC: Use LIST_HEAD() at appropriate places	2014-02-23 23:34:09 +01:00
nci	NFC: 3.15: First pull request	2014-03-17 13:16:50 -04:00
af_nfc.c
core.c	NFC: Move checking valid gb_len value to nfc_llcp_set_remote_gb	2014-03-14 20:19:08 +01:00
digital_core.c	NFC: digital: Rename Type V tags to Type 5 tags	2014-03-11 00:40:59 +01:00
digital_dep.c
digital_technology.c
digital.h
Kconfig
llcp_commands.c
llcp_core.c	net: Fix use after free by removing length arg from sk_data_ready callbacks.	2014-04-11 16:15:36 -04:00
llcp_sock.c
llcp.h
Makefile
netlink.c
nfc.h
rawsock.c