linux-kernel - [syzbot] [usb?] memory leak in class

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: <00000000000058d15f05fb264013@google.com>
Date:   Sun, 07 May 2023 20:29:50 -0700
From:   syzbot <syzbot+8d1206181166fb03c3d0@...kaller.appspotmail.com>
To:     gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        linux-usb@...r.kernel.org, rafael@...nel.org,
        syzkaller-bugs@...glegroups.com
Subject: [syzbot] [usb?] memory leak in class_register

Hello,

syzbot found the following issue on:

HEAD commit:    89b7fd5d7f3c Merge tag 'pwm/for-6.4-rc1' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=174e9388280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2a36b20e363d588f
dashboard link: https://syzkaller.appspot.com/bug?extid=8d1206181166fb03c3d0
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1343c5c4280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13e7e5d2280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/85195bfc3f96/disk-89b7fd5d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2f70e851a75/vmlinux-89b7fd5d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ab7d608fd71a/bzImage-89b7fd5d.xz

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

BUG: memory leak
unreferenced object 0xffff888101354400 (size 512):
  comm "kworker/0:1", pid 8, jiffies 4294953824 (age 15.230s)
  hex dump (first 32 bytes):
    00 44 35 01 81 88 ff ff 00 44 35 01 81 88 ff ff  .D5......D5.....
    00 00 00 00 00 00 00 00 9d 2d 9b 85 ff ff ff ff  .........-......
  backtrace:
    [<ffffffff81545854>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1057
    [<ffffffff82b673e8>] kmalloc include/linux/slab.h:559 [inline]
    [<ffffffff82b673e8>] kzalloc include/linux/slab.h:680 [inline]
    [<ffffffff82b673e8>] class_register+0x28/0x140 drivers/base/class.c:186
    [<ffffffff82b67547>] class_create+0x47/0x90 drivers/base/class.c:270
    [<ffffffff831f9ad0>] init_usb_class drivers/usb/core/file.c:91 [inline]
    [<ffffffff831f9ad0>] usb_register_dev+0x290/0x3d0 drivers/usb/core/file.c:179
    [<ffffffff832d2014>] usblp_probe+0x4e4/0x750 drivers/usb/class/usblp.c:1208
    [<ffffffff831f59f9>] usb_probe_interface+0x179/0x3c0 drivers/usb/core/driver.c:396
    [<ffffffff82b64e5d>] call_driver_probe drivers/base/dd.c:579 [inline]
    [<ffffffff82b64e5d>] really_probe+0x12d/0x430 drivers/base/dd.c:658
    [<ffffffff82b65221>] __driver_probe_device+0xc1/0x1a0 drivers/base/dd.c:800
    [<ffffffff82b6532a>] driver_probe_device+0x2a/0x120 drivers/base/dd.c:830
    [<ffffffff82b6551b>] __device_attach_driver+0xfb/0x150 drivers/base/dd.c:958
    [<ffffffff82b62271>] bus_for_each_drv+0xc1/0x110 drivers/base/bus.c:457
    [<ffffffff82b65a42>] __device_attach+0x102/0x2a0 drivers/base/dd.c:1030
    [<ffffffff82b639da>] bus_probe_device+0xca/0xd0 drivers/base/bus.c:532
    [<ffffffff82b5ffd3>] device_add+0x993/0xc60 drivers/base/core.c:3625
    [<ffffffff831f2ad9>] usb_set_configuration+0x9a9/0xc90 drivers/usb/core/message.c:2211
    [<ffffffff832053f1>] usb_generic_driver_probe+0xa1/0x100 drivers/usb/core/generic.c:238



---
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.

If the bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup