From: syzbot <syzbot+9af6d43c1beabec8fd05@syzkaller.appspotmail.com>
To: dvyukov@google.com, ebiggers@google.com, gleb@kernel.org,
gregkh@linuxfoundation.org, gwshan@linux.vnet.ibm.com,
hpa@zytor.com, jslaby@suse.com, jslaby@suse.cz,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, mpe@ellerman.id.au, pbonzini@redhat.com,
ruscur@russell.cc, stewart@linux.vnet.ibm.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: KASAN: use-after-free Read in tty_open
Date: Fri, 24 Apr 2020 17:23:03 -0700 [thread overview]
Message-ID: <0000000000002d42ee05a4127cfc@google.com> (raw)
In-Reply-To: <000000000000dd04830598d50133@google.com>
syzbot suspects this bug was fixed by commit:
commit ca4463bf8438b403596edd0ec961ca0d4fbe0220
Author: Eric Biggers <ebiggers@google.com>
Date: Sun Mar 22 03:43:04 2020 +0000
vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11594fc8100000
start commit: 07c4b9e9 Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
dashboard link: https://syzkaller.appspot.com/bug?extid=9af6d43c1beabec8fd05
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113886fae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1263520ae00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-04-25 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 23:25 KASAN: use-after-free Read in tty_open syzbot
2019-12-04 2:45 ` syzbot
2019-12-04 6:53 ` Dmitry Vyukov
2020-04-25 0:23 ` syzbot [this message]
2020-04-25 2:18 ` Eric Biggers
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=0000000000002d42ee05a4127cfc@google.com \
--to=syzbot+9af6d43c1beabec8fd05@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=gleb@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jslaby@suse.com \
--cc=jslaby@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=pbonzini@redhat.com \
--cc=ruscur@russell.cc \
--cc=stewart@linux.vnet.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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