From: syzbot <syzbot+38ee3533e07da8749f85@syzkaller.appspotmail.com>
To: liaoyu15@huawei.com
Cc: arnd@arndb.de, catalin.marinas@arm.com, liaoyu15@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, liwei391@huawei.com,
syzkaller-bugs@googlegroups.com, will@kernel.org,
zhengqi.arch@bytedance.com
Subject: Re: [syzbot] KASAN: use-after-free Write in expire_timers
Date: Tue, 22 Nov 2022 03:58:34 -0800 [thread overview]
Message-ID: <000000000000343ab505ee0de486@google.com> (raw)
In-Reply-To: <55a7be14-6ebc-2ee8-34a2-98781b32e29c@huawei.com>
> On 2022/11/22 2:35, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: b6e7fdfd6f6a Merge tag 'iommu-fixes-v6.1-rc5' of git://git..
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=11c28f95880000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=95fb379f123ba8ce
>> dashboard link: https://syzkaller.appspot.com/bug?extid=38ee3533e07da8749f85
>> compiler: aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>> userspace arch: arm64
>
> Fix data race between virtual_ncidev_close() and virtual_ncidev_open().
>
> #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
This crash does not have a reproducer. I cannot test it.
> b6e7fdfd6f6a
>
> --- a/drivers/nfc/virtual_ncidev.c
> +++ b/drivers/nfc/virtual_ncidev.c
> @@ -161,12 +161,8 @@ static int virtual_ncidev_close(struct inode *inode,
> struct file *file)
>
> if (state == virtual_ncidev_enabled) {
> state = virtual_ncidev_disabling;
> - mutex_unlock(&nci_mutex);
> -
> nci_unregister_device(ndev);
> nci_free_device(ndev);
> -
> - mutex_lock(&nci_mutex);
> }
>
> state = virtual_ncidev_disabled;
> --
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-22 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 18:35 [syzbot] KASAN: use-after-free Write in expire_timers syzbot
2022-11-22 11:57 ` Yu Liao
2022-11-22 11:58 ` syzbot [this message]
2022-11-24 6:29 ` 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=000000000000343ab505ee0de486@google.com \
--to=syzbot+38ee3533e07da8749f85@syzkaller.appspotmail.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=liaoyu15@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
--cc=zhengqi.arch@bytedance.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;
as well as URLs for NNTP newsgroup(s).