linux-kernel - memory leak in v4l2_ctrl_handler_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <00000000000013eb5105bc2bebd9@google.com>
Date:   Thu, 25 Feb 2021 08:48:17 -0800
From:   syzbot <syzbot+efe9aefc31ae1e6f7675@...kaller.appspotmail.com>
To:     ezequiel@...labora.com, hverkuil-cisco@...all.nl,
        jacopo@...ndi.org, linux-kernel@...r.kernel.org,
        linux-media@...r.kernel.org, mchehab@...nel.org,
        syzkaller-bugs@...glegroups.com
Subject: memory leak in v4l2_ctrl_handler_init_class

Hello,

syzbot found the following issue on:

HEAD commit:    c03c21ba Merge tag 'keys-misc-20210126' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1590796cd00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=24acb838051d8b5b
dashboard link: https://syzkaller.appspot.com/bug?extid=efe9aefc31ae1e6f7675
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13f1bf5ad00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=158a8632d00000

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

BUG: memory leak
unreferenced object 0xffff888110ed0800 (size 32):
  comm "kworker/0:2", pid 3639, jiffies 4294942900 (age 8.280s)
  hex dump (first 32 bytes):
    00 63 ec 0c 81 88 ff ff 00 00 00 00 00 00 00 00  .c..............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<00000000e17942dc>] kmalloc_node include/linux/slab.h:577 [inline]
    [<00000000e17942dc>] kvmalloc_node+0x61/0xf0 mm/util.c:587
    [<00000000a704dd11>] kvmalloc include/linux/mm.h:785 [inline]
    [<00000000a704dd11>] kvmalloc_array include/linux/mm.h:803 [inline]
    [<00000000a704dd11>] v4l2_ctrl_handler_init_class+0x86/0xb0 drivers/media/v4l2-core/v4l2-ctrls.c:2525
    [<0000000062f5fe33>] zr364xx_probe+0x110/0x851 drivers/media/usb/zr364xx/zr364xx.c:1427
    [<000000002a7dee6e>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
    [<0000000042b3f5b0>] really_probe+0x159/0x4a0 drivers/base/dd.c:554
    [<00000000bb6e5b5c>] driver_probe_device+0x84/0x100 drivers/base/dd.c:740
    [<00000000968b09c2>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846
    [<00000000516485c0>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
    [<000000003b640743>] __device_attach+0x122/0x250 drivers/base/dd.c:914
    [<000000008dc09474>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
    [<00000000247c2336>] device_add+0x5be/0xc30 drivers/base/core.c:3115
    [<0000000083594ecc>] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164
    [<0000000093a9f7aa>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
    [<000000000a86609a>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
    [<0000000042b3f5b0>] really_probe+0x159/0x4a0 drivers/base/dd.c:554
    [<00000000bb6e5b5c>] driver_probe_device+0x84/0x100 drivers/base/dd.c:740



---
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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches