linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: syzbot <syzbot+41f9c04b50ef70c66947@syzkaller.appspotmail.com>,
	christian.brauner@ubuntu.com, davem@davemloft.net,
	dsahern@gmail.com, fw@strlen.de, jbenc@redhat.com,
	ktkhai@virtuozzo.com, linux-kernel@vger.kernel.org,
	lucien.xin@gmail.com, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in rtnetlink_put_metrics
Date: Tue, 31 Jul 2018 15:40:14 +0200	[thread overview]
Message-ID: <20180731134014.GA32114@bistromath.localdomain> (raw)
In-Reply-To: <c8ffd001-8c67-19b9-7223-34ca8d436db2@gmail.com>

2018-07-31, 05:41:56 -0700, Eric Dumazet wrote:
> 
> 
> On 07/31/2018 05:31 AM, syzbot wrote:
> > Hello,
> > 
> > syzbot found the following crash on:
> > 
> > HEAD commit:    61f4b23769f0 netlink: Don't shift with UB on nlk->ngroups
> > git tree:       net
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14a9de58400000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=ffb4428fdc82f93b
> > dashboard link: https://syzkaller.appspot.com/bug?extid=41f9c04b50ef70c66947
> > compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
> > 
> > Unfortunately, I don't have any reproducer for this crash yet.
[...]

> Probably also caused by :
> 
> 
> commit df18b50448fab1dff093731dfd0e25e77e1afcd1
> Author: Sabrina Dubroca <sd@queasysnail.net>
> Date:   Mon Jul 30 16:23:10 2018 +0200
> 
>     net/ipv6: fix metrics leak

Yeah, I'm looking into both those reports :/

-- 
Sabrina

  reply	other threads:[~2018-07-31 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 12:31 KASAN: use-after-free Read in rtnetlink_put_metrics syzbot
2018-07-31 12:41 ` Eric Dumazet
2018-07-31 13:40   ` Sabrina Dubroca [this message]
2018-07-31 21:53     ` David Miller
2018-07-31 23:03     ` Cong Wang
2018-08-01  8:15       ` Sabrina Dubroca
2018-08-01  8:28         ` David Ahern
2018-08-02  5:23         ` Cong Wang
2018-08-01 18:46       ` David Miller
2018-08-01 19:26         ` Sabrina Dubroca

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=20180731134014.GA32114@bistromath.localdomain \
    --to=sd@queasysnail.net \
    --cc=christian.brauner@ubuntu.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=jbenc@redhat.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+41f9c04b50ef70c66947@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).