[syzbot] [media?] [usb?] memory leak in dvb_register_device

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca4ee40bf13d Partly revert "drm/hyperv: Remove reference t..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e5c722580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ee062e17a57772f
dashboard link: https://syzkaller.appspot.com/bug?extid=d37184d9d8cc34602616
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1403fe5a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d58652580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aa62e1942b0d/disk-ca4ee40b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bec89136564/vmlinux-ca4ee40b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ab4c41bad9dd/bzImage-ca4ee40b.xz

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

BUG: memory leak
unreferenced object 0xffff88812b704d80 (size 192):
comm "kworker/0:10", pid 6154, jiffies 4294943581
hex dump (first 32 bytes):
00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de ........".......
01 00 00 00 00 00 00 00 00 ec 21 04 81 88 ff ff ..........!.....
backtrace (crc 5efd1503):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4464 [inline]
slab_alloc_node mm/slub.c:4788 [inline]
__kmalloc_cache_noprof+0x377/0x480 mm/slub.c:5292
kmalloc_noprof include/linux/slab.h:962 [inline]
kzalloc_noprof include/linux/slab.h:1204 [inline]
dvb_register_device+0x116/0xaa0 drivers/media/dvb-core/dvbdev.c:475
dvb_dmxdev_init+0x116/0x1d0 drivers/media/dvb-core/dmxdev.c:1425
dvb_usbv2_adapter_dvb_init drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:484 [inline]
dvb_usbv2_adapter_init drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:801 [inline]
dvb_usbv2_init drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:866 [inline]
dvb_usbv2_probe.cold+0xc63/0xfa9 drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:981
usb_probe_interface+0x246/0x540 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:583 [inline]
really_probe+0x12f/0x3a0 drivers/base/dd.c:661
__driver_probe_device+0xc7/0x160 drivers/base/dd.c:803
driver_probe_device+0x2a/0x120 drivers/base/dd.c:833
__device_attach_driver+0x10f/0x170 drivers/base/dd.c:961
bus_for_each_drv+0xd2/0x130 drivers/base/bus.c:500
__device_attach+0xf9/0x290 drivers/base/dd.c:1033
device_initial_probe+0x6f/0x80 drivers/base/dd.c:1088
bus_probe_device+0x3e/0xb0 drivers/base/bus.c:574
device_add+0x97c/0xc80 drivers/base/core.c:3689
usb_set_configuration+0x8f5/0xb80 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0x73/0xb0 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 syzk...@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