From: syzbot <syzbot+893c55305230e719a203@syzkaller.appspotmail.com>
To: daniel.starke@siemens.com, gregkh@linuxfoundation.org,
hdanton@sina.com, jirislaby@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] KASAN: use-after-free Read in gsm_cleanup_mux
Date: Mon, 25 Sep 2023 04:55:26 -0700 [thread overview]
Message-ID: <0000000000004bd00c06062da279@google.com> (raw)
In-Reply-To: <00000000000035aab005ec690a00@google.com>
syzbot has bisected this issue to:
commit 01aecd917114577c423f07cec0d186ad007d76fc
Author: Daniel Starke <daniel.starke@siemens.com>
Date: Fri Jul 1 06:16:45 2022 +0000
tty: n_gsm: fix tty registration before control channel open
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d431ea680000
start commit: a4412fdd49dc error-injection: Add prompt for function erro..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12d431ea680000
console output: https://syzkaller.appspot.com/x/log.txt?x=14d431ea680000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc4b2e0a8e8a8366
dashboard link: https://syzkaller.appspot.com/bug?extid=893c55305230e719a203
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b1ca83880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1023c5e3880000
Reported-by: syzbot+893c55305230e719a203@syzkaller.appspotmail.com
Fixes: 01aecd917114 ("tty: n_gsm: fix tty registration before control channel open")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-25 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:52 [syzbot] KASAN: use-after-free Read in gsm_cleanup_mux syzbot
2022-12-03 4:57 ` syzbot
2023-09-25 11:55 ` syzbot [this message]
2023-10-01 4:29 ` [syzbot] [serial?] " syzbot
2023-10-02 11:40 ` Aleksandr Nogikh
[not found] <20230926111348.1208-1-hdanton@sina.com>
2023-09-26 11:38 ` syzbot
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=0000000000004bd00c06062da279@google.com \
--to=syzbot+893c55305230e719a203@syzkaller.appspotmail.com \
--cc=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.