All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f098d64cc684b8dbaf65@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] [usb?] memory leak in __hci_cmd_sync_sk
Date: Thu, 20 Nov 2025 16:34:04 -0800	[thread overview]
Message-ID: <691fb37c.a70a0220.2ea503.003c.GAE@google.com> (raw)
In-Reply-To: <tencent_9FFE8D87A5E70DFA9218DD9DDD94993F4F07@qq.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in __hci_cmd_sync_sk

BUG: memory leak
unreferenced object 0xffff88811034aa00 (size 240):
  comm "kworker/u9:0", pid 50, jiffies 4294947386
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 56103f7b):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4983 [inline]
    slab_alloc_node mm/slub.c:5288 [inline]
    kmem_cache_alloc_node_noprof+0x36f/0x5e0 mm/slub.c:5340
    __alloc_skb+0x203/0x240 net/core/skbuff.c:660
    alloc_skb include/linux/skbuff.h:1383 [inline]
    bt_skb_alloc include/net/bluetooth/bluetooth.h:510 [inline]
    hci_cmd_sync_alloc+0x30/0x140 net/bluetooth/hci_sync.c:58
    hci_cmd_sync_add net/bluetooth/hci_sync.c:99 [inline]
    __hci_cmd_sync_sk+0x7d/0x2a0 net/bluetooth/hci_sync.c:171
    __hci_cmd_sync_ev+0x3e/0x50 net/bluetooth/hci_sync.c:268
    send_hci_cmd_sync+0x5e/0xf0 net/bluetooth/mgmt.c:2615
    hci_cmd_sync_work+0xd5/0x160 net/bluetooth/hci_sync.c:350
    process_one_work+0x26b/0x620 kernel/workqueue.c:3263
    process_scheduled_works kernel/workqueue.c:3346 [inline]
    worker_thread+0x2c4/0x4f0 kernel/workqueue.c:3427
    kthread+0x15b/0x310 kernel/kthread.c:463
    ret_from_fork+0x210/0x240 arch/x86/kernel/process.c:158
    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

BUG: memory leak
unreferenced object 0xffff88810905e680 (size 704):
  comm "kworker/u9:0", pid 50, jiffies 4294947386
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 4e765d9f):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4983 [inline]
    slab_alloc_node mm/slub.c:5288 [inline]
    kmem_cache_alloc_node_noprof+0x36f/0x5e0 mm/slub.c:5340
    kmalloc_reserve+0xe6/0x180 net/core/skbuff.c:579
    __alloc_skb+0xd4/0x240 net/core/skbuff.c:670
    alloc_skb include/linux/skbuff.h:1383 [inline]
    bt_skb_alloc include/net/bluetooth/bluetooth.h:510 [inline]
    hci_cmd_sync_alloc+0x30/0x140 net/bluetooth/hci_sync.c:58
    hci_cmd_sync_add net/bluetooth/hci_sync.c:99 [inline]
    __hci_cmd_sync_sk+0x7d/0x2a0 net/bluetooth/hci_sync.c:171
    __hci_cmd_sync_ev+0x3e/0x50 net/bluetooth/hci_sync.c:268
    send_hci_cmd_sync+0x5e/0xf0 net/bluetooth/mgmt.c:2615
    hci_cmd_sync_work+0xd5/0x160 net/bluetooth/hci_sync.c:350
    process_one_work+0x26b/0x620 kernel/workqueue.c:3263
    process_scheduled_works kernel/workqueue.c:3346 [inline]
    worker_thread+0x2c4/0x4f0 kernel/workqueue.c:3427
    kthread+0x15b/0x310 kernel/kthread.c:463
    ret_from_fork+0x210/0x240 arch/x86/kernel/process.c:158
    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF


Tested on:

commit:         fd95357f Merge tag 'sched_ext-for-6.18-rc6-fixes-2' of..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=141c7a12580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44
dashboard link: https://syzkaller.appspot.com/bug?extid=f098d64cc684b8dbaf65
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=177c4484580000


  reply	other threads:[~2025-11-21  0:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 14:24 [syzbot] [bluetooth?] [usb?] memory leak in __hci_cmd_sync_sk syzbot
2025-11-18  2:53 ` Edward Adam Davis
2025-11-18  3:24   ` syzbot
2025-11-18  3:40 ` Edward Adam Davis
2025-11-18  3:54   ` syzbot
2025-11-18  3:56 ` Edward Adam Davis
2025-11-18  4:24   ` syzbot
2025-11-19  2:46 ` shaurya
2025-11-19  3:22 ` Edward Adam Davis
2025-11-19  3:47   ` syzbot
2025-11-19 18:45 ` shaurya
2025-11-19 19:32   ` syzbot
2025-11-20 13:27 ` Edward Adam Davis
2025-11-20 13:59   ` syzbot
2025-11-20 14:11 ` Edward Adam Davis
2025-11-20 14:45   ` syzbot
2025-11-20 14:54 ` Edward Adam Davis
2025-11-20 15:27   ` syzbot
2025-11-21  0:05 ` Edward Adam Davis
2025-11-21  0:34   ` syzbot [this message]
2025-11-21  0:55 ` Edward Adam Davis
2025-11-21  2:14   ` syzbot
2025-11-21  0:57 ` Edward Adam Davis
2025-11-21  2:32   ` syzbot
2025-11-21  6:17 ` Edward Adam Davis
2025-11-21  8:08   ` syzbot
2025-11-21  9:06 ` Edward Adam Davis
2025-11-21 14:36   ` syzbot
2025-11-22  7:09 ` Edward Adam Davis
2025-11-22 10:23   ` syzbot
2025-11-22 14:14 ` Edward Adam Davis
2025-11-22 14:39   ` syzbot
2025-11-23 14:05 ` Edward Adam Davis
2025-11-23 15:23   ` syzbot
2025-11-23 14:33 ` Edward Adam Davis
2025-11-23 16:09   ` syzbot
2025-11-23 15:08 ` Edward Adam Davis
2025-11-23 16:30   ` 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=691fb37c.a70a0220.2ea503.003c.GAE@google.com \
    --to=syzbot+f098d64cc684b8dbaf65@syzkaller.appspotmail.com \
    --cc=eadavis@qq.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.