netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: syzbot <syzbot+fce8f2462c403d02af98@syzkaller.appspotmail.com>,
	ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in bpf_tcp_close
Date: Mon, 2 Jul 2018 11:56:08 -0700	[thread overview]
Message-ID: <745e7f32-a886-2c7c-77e5-72bafb5105c7@gmail.com> (raw)
In-Reply-To: <000000000000ac9069056d1806c4@google.com>

On 05/26/2018 01:54 AM, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    3fb48d881dbe Merge branch 'bpf-fib-mtu-check'
> git tree:       bpf-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15fc1977800000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
> dashboard link: https://syzkaller.appspot.com/bug?extid=fce8f2462c403d02af98
> compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1310c857800000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17de7177800000
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+fce8f2462c403d02af98@syzkaller.appspotmail.com
> 
> ==================================================================


#syz fix: bpf: sockhash fix omitted bucket lock in sock_close

      parent reply	other threads:[~2018-07-02 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26  8:54 KASAN: use-after-free Read in bpf_tcp_close syzbot
2018-05-27 22:16 ` Daniel Borkmann
2018-07-02 18:56 ` John Fastabend [this message]

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=745e7f32-a886-2c7c-77e5-72bafb5105c7@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+fce8f2462c403d02af98@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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).