From: syzbot <syzbot+2fd9312f3ff65d22d06f@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, bp@suse.de, dmitry.osipenko@collabora.com,
linux-kernel@vger.kernel.org, mirq-linux@rere.qmqm.pl,
rafael.j.wysocki@intel.com, syzkaller-bugs@googlegroups.com,
vschneid@redhat.com
Subject: [syzbot] KASAN: vmalloc-out-of-bounds Read in blocking_notifier_chain_unregister
Date: Tue, 16 Aug 2022 02:06:28 -0700 [thread overview]
Message-ID: <0000000000004a37dc05e6581005@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7ebfc85e2cd7 Merge tag 'net-6.0-rc1' of git://git.kernel.o..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=160d0915080000
kernel config: https://syzkaller.appspot.com/x/.config?x=924833c12349a8c0
dashboard link: https://syzkaller.appspot.com/bug?extid=2fd9312f3ff65d22d06f
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f5b2f3080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121c0067080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2fd9312f3ff65d22d06f@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: vmalloc-out-of-bounds in notifier_chain_unregister kernel/notifier.c:51 [inline]
BUG: KASAN: vmalloc-out-of-bounds in blocking_notifier_chain_unregister+0x230/0x290 kernel/notifier.c:329
Read of size 8 at addr ffffc900038ebbe8 by task syz-executor342/3606
CPU: 1 PID: 3606 Comm: syz-executor342 Not tainted 5.19.0-syzkaller-13930-g7ebfc85e2cd7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:317 [inline]
print_report.cold+0x59/0x719 mm/kasan/report.c:433
kasan_report+0xb1/0x1e0 mm/kasan/report.c:495
notifier_chain_unregister kernel/notifier.c:51 [inline]
blocking_notifier_chain_unregister+0x230/0x290 kernel/notifier.c:329
hci_unregister_suspend_notifier+0x73/0x90 net/bluetooth/hci_core.c:2760
hci_unregister_dev+0x16f/0x4e0 net/bluetooth/hci_core.c:2678
vhci_release+0x7c/0xf0 drivers/bluetooth/hci_vhci.c:568
__fput+0x277/0x9d0 fs/file_table.c:320
task_work_run+0xdd/0x1a0 kernel/task_work.c:177
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xad5/0x29b0 kernel/exit.c:795
do_group_exit+0xd2/0x2f0 kernel/exit.c:925
__do_sys_exit_group kernel/exit.c:936 [inline]
__se_sys_exit_group kernel/exit.c:934 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:934
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f278bd0d3c9
Code: Unable to access opcode bytes at RIP 0x7f278bd0d39f.
RSP: 002b:00007ffe2fd53298 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f278bd91450 RCX: 00007f278bd0d3c9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffb8 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f278bd91450
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
</TASK>
Memory state around the buggy address:
ffffc900038eba80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc900038ebb00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc900038ebb80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
^
ffffc900038ebc00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
ffffc900038ebc80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
==================================================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-08-16 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 9:06 syzbot [this message]
[not found] <20220817111459.1148-1-hdanton@sina.com>
2022-08-17 11:52 ` [syzbot] KASAN: vmalloc-out-of-bounds Read in blocking_notifier_chain_unregister syzbot
[not found] <20220823105218.2270-1-hdanton@sina.com>
2022-08-23 11:09 ` 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=0000000000004a37dc05e6581005@google.com \
--to=syzbot+2fd9312f3ff65d22d06f@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=bp@suse.de \
--cc=dmitry.osipenko@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rafael.j.wysocki@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vschneid@redhat.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.