Oliver Hartkopp e7153bf70c can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs ... KMSAN sysbot detected a read access to an untinitialized value in the headroom of an outgoing CAN related sk_buff. When using CAN sockets this area is filled appropriately - but when using a packet socket this initialization is missing. The problematic read access occurs in the CAN receive path which can only be triggered when the sk_buff is sent through a (virtual) CAN interface. So we check in the sending path whether we need to perform the missing initializations. Fixes: d3b58c47d3 ("can: replace timestamp as unique skb attribute") Reported-by: syzbot+b02ff0707a97e4e79ebb@syzkaller.appspotmail.com Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Tested-by: Oliver Hartkopp <socketcan@hartkopp.net> Cc: linux-stable <stable@vger.kernel.org> # >= v4.1 Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>		2020-01-02 15:34:27 +01:00
..
dev
platform
can-ml.h
core.h	can: af_can: export can_sock_destruct()	2019-11-13 10:42:33 +01:00
dev.h	can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs	2020-01-02 15:34:27 +01:00
led.h
rx-offload.h	can: rx-offload: Prepare for CAN FD support	2019-11-11 21:58:10 +01:00
skb.h