ip_forward: Drop frames with attached skb->sk
Initial discussion was: [FYI] xfrm: Don't lookup sk_policy for timewait sockets Forwarded frames should not have a socket attached. Especially tw sockets will lead to panics later-on in the stack. This was observed with TPROXY assigning a tw socket and broken policy routing (misconfigured). As a result frame enters forwarding path instead of input. We cannot solve this in TPROXY as it cannot know that policy routing is broken. v2: Remove useless comment Signed-off-by: Sebastian Poehn <sebastian.poehn@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
04b7fe6a4a
commit
2ab957492d
|
@ -82,6 +82,9 @@ int ip_forward(struct sk_buff *skb)
|
|||
if (skb->pkt_type != PACKET_HOST)
|
||||
goto drop;
|
||||
|
||||
if (unlikely(skb->sk))
|
||||
goto drop;
|
||||
|
||||
if (skb_warn_if_lro(skb))
|
||||
goto drop;
|
||||
|
||||
|
|
Loading…
Reference in New Issue