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, yiyang13@huawei.com,
zhangqiumiao1@huawei.com
Subject: Re: [syzbot] [serial?] KASAN: use-after-free Read in gsm_cleanup_mux
Date: Sat, 30 Sep 2023 21:29:23 -0700 [thread overview]
Message-ID: <0000000000002b41f10606a01a89@google.com> (raw)
In-Reply-To: <00000000000035aab005ec690a00@google.com>
syzbot suspects this issue was fixed by commit:
commit 3c4f8333b582487a2d1e02171f1465531cde53e3
Author: Yi Yang <yiyang13@huawei.com>
Date: Fri Aug 11 03:11:21 2023 +0000
tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=121e6a92680000
start commit: a4412fdd49dc error-injection: Add prompt for function erro..
git tree: upstream
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
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-01 4:29 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] [serial?] " syzbot
2023-10-01 4:29 ` syzbot [this message]
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=0000000000002b41f10606a01a89@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 \
--cc=yiyang13@huawei.com \
--cc=zhangqiumiao1@huawei.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.