summaryrefslogtreecommitdiff
path: root/include/linux/bcm963xx_nvram.h
diff options
context:
space:
mode:
authorBalazs Nemeth <bnemeth@redhat.com>2021-03-09 14:31:00 +0300
committerDavid S. Miller <davem@davemloft.net>2021-03-10 03:12:20 +0300
commit924a9bc362a5223cd448ca08c3dde21235adc310 (patch)
tree39c880b0dd7a77a7c0c870f8e1b36f3dad6d46c4 /include/linux/bcm963xx_nvram.h
parent286a8624d7f9c6505cd568d947772eb59646514b (diff)
downloadlinux-924a9bc362a5223cd448ca08c3dde21235adc310.tar.xz
net: check if protocol extracted by virtio_net_hdr_set_proto is correct
For gso packets, virtio_net_hdr_set_proto sets the protocol (if it isn't set) based on the type in the virtio net hdr, but the skb could contain anything since it could come from packet_snd through a raw socket. If there is a mismatch between what virtio_net_hdr_set_proto sets and the actual protocol, then the skb could be handled incorrectly later on. An example where this poses an issue is with the subsequent call to skb_flow_dissect_flow_keys_basic which relies on skb->protocol being set correctly. A specially crafted packet could fool skb_flow_dissect_flow_keys_basic preventing EINVAL to be returned. Avoid blindly trusting the information provided by the virtio net header by checking that the protocol in the packet actually matches the protocol set by virtio_net_hdr_set_proto. Note that since the protocol is only checked if skb->dev implements header_ops->parse_protocol, packets from devices without the implementation are not checked at this stage. Fixes: 9274124f023b ("net: stricter validation of untrusted gso packets") Signed-off-by: Balazs Nemeth <bnemeth@redhat.com> Acked-by: Willem de Bruijn <willemb@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux/bcm963xx_nvram.h')
0 files changed, 0 insertions, 0 deletions