From: syzbot <syzbot+a41b73dce23962a74c72@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [media?] [usb?] memory leak in v4l2_ctrl_handler_init_class (2)
Date: Mon, 24 Nov 2025 23:55:24 -0800 [thread overview]
Message-ID: <692560ec.a70a0220.2ea503.0087.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: fd95357fd8c6 Merge tag 'sched_ext-for-6.18-rc6-fixes-2' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a39742580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44
dashboard link: https://syzkaller.appspot.com/bug?extid=a41b73dce23962a74c72
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b05a12580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f8aa12580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/23b612a7fe35/disk-fd95357f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2da12b65fa76/vmlinux-fd95357f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/97ebacdc6971/bzImage-fd95357f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a41b73dce23962a74c72@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88812a347a58 (size 8):
comm "kworker/0:6", pid 6036, jiffies 4294942408
hex dump (first 8 bytes):
80 38 6e 25 81 88 ff ff .8n%....
backtrace (crc f78d2928):
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]
__do_kmalloc_node mm/slub.c:5649 [inline]
__kvmalloc_node_noprof+0x51c/0x820 mm/slub.c:7112
kvmalloc_array_node_noprof include/linux/slab.h:1122 [inline]
v4l2_ctrl_handler_init_class+0x67/0x90 drivers/media/v4l2-core/v4l2-ctrls-core.c:1625
usb_keene_probe+0xc4/0x450 drivers/media/radio/radio-keene.c:326
usb_probe_interface+0x173/0x3f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
__driver_probe_device+0xc3/0x1a0 drivers/base/dd.c:801
driver_probe_device+0x2a/0x120 drivers/base/dd.c:831
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:959
bus_for_each_drv+0xcf/0x120 drivers/base/bus.c:462
__device_attach+0xf9/0x290 drivers/base/dd.c:1031
bus_probe_device+0xcd/0xe0 drivers/base/bus.c:537
device_add+0x983/0xc80 drivers/base/core.c:3689
usb_set_configuration+0x961/0xc70 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x83/0xd0 drivers/usb/core/generic.c:250
usb_probe_device+0x7c/0x1d0 drivers/usb/core/driver.c:291
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
BUG: memory leak
unreferenced object 0xffff888126df0200 (size 256):
comm "kworker/0:6", pid 6036, jiffies 4294942408
hex dump (first 32 bytes):
00 0b df 26 81 88 ff ff 00 09 df 26 81 88 ff ff ...&.......&....
10 02 df 26 81 88 ff ff 10 02 df 26 81 88 ff ff ...&.......&....
backtrace (crc 602da918):
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]
__do_kmalloc_node mm/slub.c:5649 [inline]
__kvmalloc_node_noprof+0x51c/0x820 mm/slub.c:7112
v4l2_ctrl_new+0x2bf/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2031
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
usb_keene_probe+0xe8/0x450 drivers/media/radio/radio-keene.c:327
usb_probe_interface+0x173/0x3f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
__driver_probe_device+0xc3/0x1a0 drivers/base/dd.c:801
driver_probe_device+0x2a/0x120 drivers/base/dd.c:831
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:959
bus_for_each_drv+0xcf/0x120 drivers/base/bus.c:462
__device_attach+0xf9/0x290 drivers/base/dd.c:1031
bus_probe_device+0xcd/0xe0 drivers/base/bus.c:537
device_add+0x983/0xc80 drivers/base/core.c:3689
usb_set_configuration+0x961/0xc70 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x83/0xd0 drivers/usb/core/generic.c:250
usb_probe_device+0x7c/0x1d0 drivers/usb/core/driver.c:291
BUG: memory leak
unreferenced object 0xffff888126df0900 (size 256):
comm "kworker/0:6", pid 6036, jiffies 4294942408
hex dump (first 32 bytes):
00 02 df 26 81 88 ff ff 30 f5 8f 24 81 88 ff ff ...&....0..$....
10 09 df 26 81 88 ff ff 10 09 df 26 81 88 ff ff ...&.......&....
backtrace (crc 84e60c55):
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]
__do_kmalloc_node mm/slub.c:5649 [inline]
__kvmalloc_node_noprof+0x51c/0x820 mm/slub.c:7112
v4l2_ctrl_new+0x2bf/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2031
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
handler_new_ref+0x352/0x450 drivers/media/v4l2-core/v4l2-ctrls-core.c:1772
v4l2_ctrl_new+0x67d/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2114
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
usb_keene_probe+0xe8/0x450 drivers/media/radio/radio-keene.c:327
usb_probe_interface+0x173/0x3f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
__driver_probe_device+0xc3/0x1a0 drivers/base/dd.c:801
driver_probe_device+0x2a/0x120 drivers/base/dd.c:831
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:959
bus_for_each_drv+0xcf/0x120 drivers/base/bus.c:462
__device_attach+0xf9/0x290 drivers/base/dd.c:1031
bus_probe_device+0xcd/0xe0 drivers/base/bus.c:537
device_add+0x983/0xc80 drivers/base/core.c:3689
BUG: memory leak
unreferenced object 0xffff8881256e3400 (size 64):
comm "kworker/0:6", pid 6036, jiffies 4294942408
hex dump (first 32 bytes):
40 33 6e 25 81 88 ff ff 40 f5 8f 24 81 88 ff ff @3n%....@..$....
00 00 00 00 00 00 00 00 00 09 df 26 81 88 ff ff ...........&....
backtrace (crc a7c4a093):
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]
__do_kmalloc_node mm/slub.c:5649 [inline]
__kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5662
kmalloc_noprof include/linux/slab.h:961 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
handler_new_ref+0xd7/0x450 drivers/media/v4l2-core/v4l2-ctrls-core.c:1780
v4l2_ctrl_new+0x67d/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2114
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
handler_new_ref+0x352/0x450 drivers/media/v4l2-core/v4l2-ctrls-core.c:1772
v4l2_ctrl_new+0x67d/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2114
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
usb_keene_probe+0xe8/0x450 drivers/media/radio/radio-keene.c:327
usb_probe_interface+0x173/0x3f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
__driver_probe_device+0xc3/0x1a0 drivers/base/dd.c:801
driver_probe_device+0x2a/0x120 drivers/base/dd.c:831
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:959
bus_for_each_drv+0xcf/0x120 drivers/base/bus.c:462
__device_attach+0xf9/0x290 drivers/base/dd.c:1031
bus_probe_device+0xcd/0xe0 drivers/base/bus.c:537
BUG: memory leak
unreferenced object 0xffff8881256e3340 (size 64):
comm "kworker/0:6", pid 6036, jiffies 4294942408
hex dump (first 32 bytes):
80 32 6e 25 81 88 ff ff 00 34 6e 25 81 88 ff ff .2n%.....4n%....
00 34 6e 25 81 88 ff ff 00 02 df 26 81 88 ff ff .4n%.......&....
backtrace (crc be938ee5):
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]
__do_kmalloc_node mm/slub.c:5649 [inline]
__kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5662
kmalloc_noprof include/linux/slab.h:961 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
handler_new_ref+0xd7/0x450 drivers/media/v4l2-core/v4l2-ctrls-core.c:1780
v4l2_ctrl_new+0x67d/0x1340 drivers/media/v4l2-core/v4l2-ctrls-core.c:2114
v4l2_ctrl_new_std+0x122/0x180 drivers/media/v4l2-core/v4l2-ctrls-core.c:2185
usb_keene_probe+0xe8/0x450 drivers/media/radio/radio-keene.c:327
usb_probe_interface+0x173/0x3f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x12f/0x430 drivers/base/dd.c:659
__driver_probe_device+0xc3/0x1a0 drivers/base/dd.c:801
driver_probe_device+0x2a/0x120 drivers/base/dd.c:831
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:959
bus_for_each_drv+0xcf/0x120 drivers/base/bus.c:462
__device_attach+0xf9/0x290 drivers/base/dd.c:1031
bus_probe_device+0xcd/0xe0 drivers/base/bus.c:537
device_add+0x983/0xc80 drivers/base/core.c:3689
usb_set_configuration+0x961/0xc70 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x83/0xd0 drivers/usb/core/generic.c:250
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2025-11-25 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:55 syzbot [this message]
2025-11-25 17:01 ` [syzbot] [media?] [usb?] memory leak in v4l2_ctrl_handler_init_class (2) shaurya
2025-11-25 20:38 ` syzbot
2025-11-25 17:03 ` shaurya
2025-11-25 21:09 ` syzbot
2025-11-25 20:21 ` shaurya
2025-11-25 21:29 ` 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=692560ec.a70a0220.2ea503.0087.GAE@google.com \
--to=syzbot+a41b73dce23962a74c72@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@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.