[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVxrUinOBjqaw4U5u9PZZSTDY=FgSAsBxMju8uu=F5jfQ@mail.gmail.com>
Date: Mon, 29 Jun 2020 20:33:48 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: syzbot <syzbot+a82be85e09cd5df398fe@...kaller.appspotmail.com>,
Johannes Berg <johannes@...solutions.net>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
WireGuard mailing list <wireguard@...ts.zx2c4.com>
Subject: Re: KASAN: use-after-free Read in netdev_name_node_lookup_rcu
On Mon, Jun 29, 2020 at 6:17 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
>
> Hey Cong,
Hi, Jason
>
> I'm wondering if the below error is related to what you've been
> looking at yesterday. AFAICT, there's a simple UaF on the attrbuf
> passed to the start method. I recall recently you were working on the
> locking in genetlink's family buffers and wound up mallocing some
> things, so it seems like this might be related. See below.
Yeah, very likely it is the same bug I have fixed. I will close
this together with others.
Thanks.
Powered by blists - more mailing lists