From: Cong Wang <xiyou.wangcong@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Anoob Soman <anoob.soman@citrix.com>,
David Miller <davem@davemloft.net>,
Willem de Bruijn <willemb@google.com>,
Eric Dumazet <edumazet@google.com>,
Daniel Borkmann <daniel@iogearbox.net>,
jarno@ovn.org, Philip Pettersson <philip.pettersson@gmail.com>,
weongyo.linux@gmail.com, netdev <netdev@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: net/packet: use-after-free in packet_rcv_fanout
Date: Fri, 17 Feb 2017 11:27:15 -0800 [thread overview]
Message-ID: <CAM_iQpUDhakMjof97qWvyLFXiDMiL6FUv+5OzGTPbnCXZp=Pzw@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+bdZRYC5EyifuqBQWNNZ-sHBDXyVBvnzPCq8eg4-SHJ9Q@mail.gmail.com>
On Mon, Feb 13, 2017 at 7:17 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
>
> Another similar one:
>
The other possibility is: __fanout_link() is called twice on the same
packet sock
for some reason, but __fanout_unlink() only unlinks the first one, which led to
this use-after-free. However, the po->running and po->fanout seem enough
to guarantee this should not happen. I still want to point this out in case I
miss anything here so that other people could figure it out.
next prev parent reply other threads:[~2017-02-17 19:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:14 net/packet: use-after-free in packet_rcv_fanout Dmitry Vyukov
2017-02-09 15:12 ` Sowmini Varadhan
2017-02-09 15:17 ` Eric Dumazet
2017-02-10 1:24 ` Cong Wang
2017-02-10 3:19 ` Eric Dumazet
2017-02-10 3:23 ` Eric Dumazet
2017-02-10 17:49 ` Cong Wang
2017-02-10 17:59 ` Eric Dumazet
2017-02-10 18:02 ` Cong Wang
2017-02-10 18:15 ` Eric Dumazet
2017-02-10 18:02 ` Eric Dumazet
2017-02-10 18:34 ` Cong Wang
2017-02-13 1:42 ` Sowmini Varadhan
2017-02-13 15:17 ` Dmitry Vyukov
2017-02-17 19:27 ` Cong Wang [this message]
2017-02-10 3:33 ` Sowmini Varadhan
2017-02-10 4:18 ` Eric Dumazet
2017-02-10 18:00 ` Cong Wang
2017-02-10 19:16 ` Sowmini Varadhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM_iQpUDhakMjof97qWvyLFXiDMiL6FUv+5OzGTPbnCXZp=Pzw@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=anoob.soman@citrix.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jarno@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=philip.pettersson@gmail.com \
--cc=sowmini.varadhan@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=weongyo.linux@gmail.com \
--cc=willemb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).