From: Al Viro <viro@ZenIV.linux.org.uk>
To: syzbot
<bot+7f44246e4b515a3908f27c3ac65d68c7c6cb4544@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in __fput
Date: Mon, 4 Dec 2017 16:44:52 +0000 [thread overview]
Message-ID: <20171204164452.GT21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <001a1146fbf6a6305c055cfdf55e@google.com>
On Thu, Nov 02, 2017 at 04:05:01AM -0700, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 3a99df9a3d14cd866b5516f8cba515a3bfd554ab
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
That one is almost certainly double-free in kcm_clone() fixed in
https://marc.info/?l=linux-netdev&m=151208776817071&q=raw
next parent reply other threads:[~2017-12-04 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1146fbf6a6305c055cfdf55e@google.com>
2017-12-04 16:44 ` Al Viro [this message]
2017-12-04 18:39 ` KASAN: use-after-free Read in __fput Dmitry Vyukov
2017-12-04 18:43 ` Al Viro
2018-02-12 16:13 ` Dmitry Vyukov
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=20171204164452.GT21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bot+7f44246e4b515a3908f27c3ac65d68c7c6cb4544@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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