[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1397092959.16584.26.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 09 Apr 2014 18:22:39 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: David Miller <davem@...emloft.net>
Cc: netdev <netdev@...r.kernel.org>, Xi Wang <xii@...gle.com>
Subject: [PATCH] packet: fix potential use after free
From: Eric Dumazet <edumazet@...gle.com>
As soon skb is queued into sk_receive_queue, it can be consumed,
so its racy to access skb->len.
Given that sk_data_ready() / sock_def_readable() don't really care, just
use 0 instead of skb->len
Signed-off-by: Eric Dumazet <edumazet@...gle.com>
Cc: Xi Wang <xii@...gle.com>
---
net/packet/af_packet.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
index 72e0c71fb01d..373d557e22ee 100644
--- a/net/packet/af_packet.c
+++ b/net/packet/af_packet.c
@@ -1848,7 +1848,8 @@ static int packet_rcv(struct sk_buff *skb, struct net_device *dev,
skb->dropcount = atomic_read(&sk->sk_drops);
__skb_queue_tail(&sk->sk_receive_queue, skb);
spin_unlock(&sk->sk_receive_queue.lock);
- sk->sk_data_ready(sk, skb->len);
+ /* Remember: we can not reference skb after this point */
+ sk->sk_data_ready(sk, 0);
return 0;
drop_n_acct:
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists