All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
	 linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt
Date: Sun, 23 Feb 2025 23:19:24 -0800	[thread overview]
Message-ID: <67bc1d7c.050a0220.bbfd1.0045.GAE@google.com> (raw)
In-Reply-To: <67389a73.050a0220.bb738.000a.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    d082ecbc71e9 Linux 6.14-rc4
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13492db0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d66f6f82ee090382
dashboard link: https://syzkaller.appspot.com/bug?extid=a9a4bedfca6aa9d7fa24
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=122c37f8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10023fdf980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9f22e75faf0/disk-d082ecbc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/336a72a11410/vmlinux-d082ecbc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7180e4935c41/bzImage-d082ecbc.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com

=====================================================
BUG: KMSAN: uninit-value in hci_cmd_complete_evt+0xd7b/0xeb0 net/bluetooth/hci_event.c:4226
 hci_cmd_complete_evt+0xd7b/0xeb0 net/bluetooth/hci_event.c:4226
 hci_event_func net/bluetooth/hci_event.c:7470 [inline]
 hci_event_packet+0x11c8/0x1ca0 net/bluetooth/hci_event.c:7525
 hci_rx_work+0x699/0x1260 net/bluetooth/hci_core.c:4015
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xc1a/0x1e80 kernel/workqueue.c:3317
 worker_thread+0xea7/0x14f0 kernel/workqueue.c:3398
 kthread+0x6b9/0xef0 kernel/kthread.c:464
 ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

Uninit was stored to memory at:
 hci_cmd_complete_evt+0xaf4/0xeb0
 hci_event_func net/bluetooth/hci_event.c:7470 [inline]
 hci_event_packet+0x11c8/0x1ca0 net/bluetooth/hci_event.c:7525
 hci_rx_work+0x699/0x1260 net/bluetooth/hci_core.c:4015
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xc1a/0x1e80 kernel/workqueue.c:3317
 worker_thread+0xea7/0x14f0 kernel/workqueue.c:3398
 kthread+0x6b9/0xef0 kernel/kthread.c:464
 ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

Uninit was created at:
 slab_post_alloc_hook mm/slub.c:4121 [inline]
 slab_alloc_node mm/slub.c:4164 [inline]
 kmem_cache_alloc_node_noprof+0x907/0xe00 mm/slub.c:4216
 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:515
 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:606
 alloc_skb include/linux/skbuff.h:1331 [inline]
 bt_skb_alloc include/net/bluetooth/bluetooth.h:495 [inline]
 vhci_get_user drivers/bluetooth/hci_vhci.c:487 [inline]
 vhci_write+0x127/0x900 drivers/bluetooth/hci_vhci.c:607
 new_sync_write fs/read_write.c:586 [inline]
 vfs_write+0xb34/0x1540 fs/read_write.c:679
 ksys_write+0x240/0x4b0 fs/read_write.c:731
 __do_sys_write fs/read_write.c:742 [inline]
 __se_sys_write fs/read_write.c:739 [inline]
 __x64_sys_write+0x93/0xe0 fs/read_write.c:739
 x64_sys_call+0x3161/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:2
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

CPU: 1 UID: 0 PID: 5777 Comm: kworker/u9:2 Not tainted 6.14.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: hci0 hci_rx_work
=====================================================


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

  reply	other threads:[~2025-02-24  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 13:13 [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt syzbot
2025-02-24  7:19 ` syzbot [this message]
2025-07-22  2:15 ` Forwarded: " syzbot
2025-10-02 17:04 ` Forwarded: " syzbot
2025-10-21 22:08 ` Forwarded: test fix syzbot
2025-10-24 15:41 ` syzbot
     [not found] <ank5qnbeu55cd7vktzjd2iagozehy62m4v7bbapnmsbxcks5zv@xb6nlrhtsk6x>
2025-07-22  6:03 ` [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt syzbot
     [not found] <CAOeBcHMF2n1Bf5Tdx1kd9kPOAg-nCofANxY_RfV7VmObdvCgeQ@mail.gmail.com>
2025-10-02 17:29 ` syzbot
     [not found] <aPgEdIAnSTBroJuS@rpthibeault-XPS-13-9305>
2025-10-22  5:22 ` syzbot
     [not found] <aPueHB4AaBdRL9hL@rpthibeault-XPS-13-9305>
2025-10-24 16:11 ` 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=67bc1d7c.050a0220.bbfd1.0045.GAE@google.com \
    --to=syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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.