From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: syzbot <syzbot+37100ea87beb0cac28f4@syzkaller.appspotmail.com>,
acme@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, jolsa@redhat.com, kafai@fb.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
namhyung@kernel.org, netdev@vger.kernel.org,
peterz@infradead.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com
Subject: Re: KASAN: use-after-free Read in _free_event
Date: Mon, 24 Jun 2019 11:39:00 +0300 [thread overview]
Message-ID: <87pnn3v0m3.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <000000000000dea828058c0d815d@google.com>
syzbot <syzbot+37100ea87beb0cac28f4@syzkaller.appspotmail.com> writes:
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+37100ea87beb0cac28f4@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: use-after-free in atomic_read
> include/asm-generic/atomic-instrumented.h:26 [inline]
> BUG: KASAN: use-after-free in refcount_sub_and_test_checked+0x87/0x200
> lib/refcount.c:182
> Read of size 4 at addr ffff88804e9f06e0 by task syz-executor.5/13046
Looks exactly like [1]. There's a proposed fix there, too.
[1] https://marc.info/?l=linux-kernel&m=153111554522295
Regards,
--
Alex
prev parent reply other threads:[~2019-06-24 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 8:22 KASAN: use-after-free Read in _free_event syzbot
2019-06-24 8:39 ` Alexander Shishkin [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=87pnn3v0m3.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzbot+37100ea87beb0cac28f4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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