android_kernel_samsung_msm8976/include/net/sctp
Dan Carpenter 0a900adda7 sctp: potential read out of bounds in sctp_ulpevent_type_enabled()
commit fa5f7b51fc3080c2b195fa87c7eca7c05e56f673 upstream.

This code causes a static checker warning because Smatch doesn't trust
anything that comes from skb->data.  I've reviewed this code and I do
think skb->data can be controlled by the user here.

The sctp_event_subscribe struct has 13 __u8 fields and we want to see
if ours is non-zero.  sn_type can be any value in the 0-USHRT_MAX range.
We're subtracting SCTP_SN_TYPE_BASE which is 1 << 15 so we could read
either before the start of the struct or after the end.

This is a very old bug and it's surprising that it would go undetected
for so long but my theory is that it just doesn't have a big impact so
it would be hard to notice.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Willy Tarreau <w@1wt.eu>
2019-07-27 21:44:28 +02:00
..
auth.h
checksum.h
command.h
constants.h
sctp.h sctp: fix the check for _sctp_walk_params and _sctp_walk_errors 2019-07-27 21:44:27 +02:00
sm.h net: sctp: fix skb_over_panic when receiving malformed ASCONF chunks 2014-11-21 09:22:55 -08:00
structs.h sctp: fix ASCONF list handling 2015-10-01 12:07:34 +02:00
tsnmap.h
ulpevent.h sctp: potential read out of bounds in sctp_ulpevent_type_enabled() 2019-07-27 21:44:28 +02:00
ulpqueue.h