From: syzbot <syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com>
To: chelsyratnawat2001@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt
Date: Thu, 02 Oct 2025 10:29:02 -0700 [thread overview]
Message-ID: <68deb65e.a00a0220.102ee.00df.GAE@google.com> (raw)
In-Reply-To: <CAOeBcHMF2n1Bf5Tdx1kd9kPOAg-nCofANxY_RfV7VmObdvCgeQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in hci_cmd_complete_evt
=====================================================
BUG: KMSAN: uninit-value in hci_cmd_complete_evt+0xca3/0xe90 net/bluetooth/hci_event.c:4226
hci_cmd_complete_evt+0xca3/0xe90 net/bluetooth/hci_event.c:4226
hci_event_func net/bluetooth/hci_event.c:7566 [inline]
hci_event_packet+0xcdf/0x1e40 net/bluetooth/hci_event.c:7623
hci_rx_work+0x9a8/0x12b0 net/bluetooth/hci_core.c:4071
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xb91/0x1d80 kernel/workqueue.c:3346
worker_thread+0xedf/0x1590 kernel/workqueue.c:3427
kthread+0xd5c/0xf00 kernel/kthread.c:463
ret_from_fork+0x233/0x380 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was stored to memory at:
hci_cmd_complete_evt+0xc9c/0xe90 net/bluetooth/hci_event.c:4226
hci_event_func net/bluetooth/hci_event.c:7566 [inline]
hci_event_packet+0xcdf/0x1e40 net/bluetooth/hci_event.c:7623
hci_rx_work+0x9a8/0x12b0 net/bluetooth/hci_core.c:4071
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xb91/0x1d80 kernel/workqueue.c:3346
worker_thread+0xedf/0x1590 kernel/workqueue.c:3427
kthread+0xd5c/0xf00 kernel/kthread.c:463
ret_from_fork+0x233/0x380 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was stored to memory at:
hci_cmd_complete_evt+0x775/0xe90 net/bluetooth/hci_event.c:-1
hci_event_func net/bluetooth/hci_event.c:7566 [inline]
hci_event_packet+0xcdf/0x1e40 net/bluetooth/hci_event.c:7623
hci_rx_work+0x9a8/0x12b0 net/bluetooth/hci_core.c:4071
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xb91/0x1d80 kernel/workqueue.c:3346
worker_thread+0xedf/0x1590 kernel/workqueue.c:3427
kthread+0xd5c/0xf00 kernel/kthread.c:463
ret_from_fork+0x233/0x380 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4197 [inline]
slab_alloc_node mm/slub.c:4240 [inline]
kmem_cache_alloc_node_noprof+0x818/0xf00 mm/slub.c:4292
kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:578
__alloc_skb+0x347/0x7d0 net/core/skbuff.c:669
alloc_skb include/linux/skbuff.h:1336 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:509 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:496 [inline]
vhci_write+0x129/0x980 drivers/bluetooth/hci_vhci.c:617
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0xbe2/0x15d0 fs/read_write.c:686
ksys_write fs/read_write.c:738 [inline]
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746
x64_sys_call+0x3014/0x3e30 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 5862 Comm: kworker/u9:2 Not tainted syzkaller #0 PREEMPT(none)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: hci0 hci_rx_work
=====================================================
Tested on:
commit: 7f707257 Merge tag 'kbuild-6.18-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10c065cd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=40e84ec1e5456fca
dashboard link: https://syzkaller.appspot.com/bug?extid=a9a4bedfca6aa9d7fa24
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=117fa5cd980000
next parent reply other threads:[~2025-10-02 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOeBcHMF2n1Bf5Tdx1kd9kPOAg-nCofANxY_RfV7VmObdvCgeQ@mail.gmail.com>
2025-10-02 17:29 ` syzbot [this message]
[not found] <aPueHB4AaBdRL9hL@rpthibeault-XPS-13-9305>
2025-10-24 16:11 ` [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt syzbot
[not found] <aPgEdIAnSTBroJuS@rpthibeault-XPS-13-9305>
2025-10-22 5:22 ` syzbot
[not found] <ank5qnbeu55cd7vktzjd2iagozehy62m4v7bbapnmsbxcks5zv@xb6nlrhtsk6x>
2025-07-22 6:03 ` syzbot
2024-11-16 13:13 syzbot
2025-02-24 7:19 ` 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=68deb65e.a00a0220.102ee.00df.GAE@google.com \
--to=syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com \
--cc=chelsyratnawat2001@gmail.com \
--cc=linux-kernel@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.