From: syzbot <syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] memory leak in hub_event (4)
Date: Sat, 25 Apr 2026 00:13:01 -0700 [thread overview]
Message-ID: <69ec697d.a00a0220.1901e8.0006.GAE@google.com> (raw)
In-Reply-To: <20260425063629.59918-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in hub_event
BUG: memory leak
unreferenced object 0xffff8881149d6000 (size 2048):
comm "kworker/0:2", pid 807, jiffies 4294949998
hex dump (first 32 bytes):
ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00 ....1...........
00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 ................
backtrace (crc 6a8f68af):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4574 [inline]
slab_alloc_node mm/slub.c:4898 [inline]
__kmalloc_cache_noprof+0x371/0x480 mm/slub.c:5410
kmalloc_noprof include/linux/slab.h:950 [inline]
kzalloc_noprof include/linux/slab.h:1188 [inline]
usb_alloc_dev+0x36/0x4e0 drivers/usb/core/usb.c:651
hub_port_connect drivers/usb/core/hub.c:5471 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5708 [inline]
port_event drivers/usb/core/hub.c:5872 [inline]
hub_event+0x14d0/0x2180 drivers/usb/core/hub.c:5954
process_one_work+0x277/0x5b0 kernel/workqueue.c:3302
process_scheduled_works kernel/workqueue.c:3385 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3466
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff888129f4a800 (size 256):
comm "kworker/0:2", pid 807, jiffies 4294950032
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 08 a8 f4 29 81 88 ff ff ...........)....
08 a8 f4 29 81 88 ff ff b0 7d 41 83 ff ff ff ff ...).....}A.....
backtrace (crc c705f08):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4574 [inline]
slab_alloc_node mm/slub.c:4898 [inline]
__kmalloc_cache_noprof+0x371/0x480 mm/slub.c:5410
kmalloc_noprof include/linux/slab.h:950 [inline]
kzalloc_noprof include/linux/slab.h:1188 [inline]
device_private_init drivers/base/core.c:3536 [inline]
device_add+0x73c/0xc70 drivers/base/core.c:3587
usb_new_device.cold+0x115/0x633 drivers/usb/core/hub.c:2695
hub_port_connect drivers/usb/core/hub.c:5568 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5708 [inline]
port_event drivers/usb/core/hub.c:5872 [inline]
hub_event+0x1723/0x2180 drivers/usb/core/hub.c:5954
process_one_work+0x277/0x5b0 kernel/workqueue.c:3302
process_scheduled_works kernel/workqueue.c:3385 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3466
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 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: 27d128c1 Merge tag 'trace-ring-buffer-v7.1-3' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a91c36580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9645c21cfd1d3e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=2afd7e71155c7e241560
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=1027e2ce580000
next parent reply other threads:[~2026-04-25 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260425063629.59918-1-kartikey406@gmail.com>
2026-04-25 7:13 ` syzbot [this message]
[not found] <20260425144309.67569-1-kartikey406@gmail.com>
2026-04-25 15:23 ` [syzbot] [usb?] memory leak in hub_event (4) syzbot
[not found] <20260425125451.64534-1-kartikey406@gmail.com>
2026-04-25 14:09 ` syzbot
[not found] <20260425093612.30657-1-souradiptodas6@gmail.com>
2026-04-25 10:11 ` syzbot
[not found] <CAKVbAB1UYCWwpZvmV05TuA_NU16YY6fEr5t0HUjuixVq_f5b+w@mail.gmail.com>
2026-04-25 9:51 ` syzbot
[not found] <20260425075154.61497-1-kartikey406@gmail.com>
2026-04-25 8:41 ` syzbot
2026-04-25 2:12 syzbot
2026-04-27 11:40 ` Oliver Neukum
2026-04-27 12:37 ` syzbot
2026-04-27 14:19 ` Alan Stern
2026-04-28 11:33 ` Oliver Neukum
2026-04-28 15:12 ` Alan Stern
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=69ec697d.a00a0220.1901e8.0006.GAE@google.com \
--to=syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com \
--cc=kartikey406@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.