From: syzbot <syzbot+dcb7d98a388eafb85ecb@syzkaller.appspotmail.com>
To: davem@davemloft.net, glider@google.com, johan.hedberg@gmail.com,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] KMSAN: uninit-value in hci_conn_complete_evt
Date: Sun, 28 Nov 2021 01:22:17 -0800 [thread overview]
Message-ID: <00000000000047549805d1d5dcdc@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a535b0caaa2f Revert "DO-NOT-SUBMIT: kmsan: suppress a repo..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=10becf06b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d142cdf4204061
dashboard link: https://syzkaller.appspot.com/bug?extid=dcb7d98a388eafb85ecb
compiler: clang version 14.0.0 (git@github.com:llvm/llvm-project.git 0996585c8e3b3d409494eb5f1cad714b9e1f7fb5), GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dcb7d98a388eafb85ecb@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in hci_conn_complete_evt+0x8e7/0x1de0 net/bluetooth/hci_event.c:2668
hci_conn_complete_evt+0x8e7/0x1de0 net/bluetooth/hci_event.c:2668
hci_event_packet+0x1670/0x22e0 net/bluetooth/hci_event.c:6311
hci_rx_work+0x6ae/0xd10 net/bluetooth/hci_core.c:5136
process_one_work+0xdc7/0x1760 kernel/workqueue.c:2297
worker_thread+0x1101/0x22b0 kernel/workqueue.c:2444
kthread+0x66b/0x780 kernel/kthread.c:319
ret_from_fork+0x1f/0x30
Uninit was created at:
slab_post_alloc_hook mm/slab.h:524 [inline]
slab_alloc_node mm/slub.c:3227 [inline]
__kmalloc_node_track_caller+0xa3b/0x13c0 mm/slub.c:4962
kmalloc_reserve net/core/skbuff.c:356 [inline]
__alloc_skb+0x4db/0xe40 net/core/skbuff.c:427
alloc_skb include/linux/skbuff.h:1116 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:389 [inline]
bcsp_recv+0x1550/0x2120 drivers/bluetooth/hci_bcsp.c:673
hci_uart_tty_receive+0x345/0x7a0 drivers/bluetooth/hci_ldisc.c:613
tty_ldisc_receive_buf+0x32a/0x390 drivers/tty/tty_buffer.c:475
tty_port_default_receive_buf+0x14b/0x1e0 drivers/tty/tty_port.c:39
receive_buf drivers/tty/tty_buffer.c:491 [inline]
flush_to_ldisc+0x3b5/0x940 drivers/tty/tty_buffer.c:543
process_one_work+0xdc7/0x1760 kernel/workqueue.c:2297
worker_thread+0x1101/0x22b0 kernel/workqueue.c:2444
kthread+0x66b/0x780 kernel/kthread.c:319
ret_from_fork+0x1f/0x30
=====================================================
---
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.
reply other threads:[~2021-11-28 9:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00000000000047549805d1d5dcdc@google.com \
--to=syzbot+dcb7d98a388eafb85ecb@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=glider@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@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 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).