linux-kernel - memory leak in ath9k_hif_usb_firmware

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: <0000000000000335e105b3c4cd69@google.com>
Date:   Tue, 10 Nov 2020 10:25:18 -0800
From:   syzbot <syzbot+6692c72009680f7c4eb2@...kaller.appspotmail.com>
To:     eli.billauer@...il.com, gregkh@...uxfoundation.org,
        gustavoars@...nel.org, ingrassia@...genesys.com,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        stern@...land.harvard.edu, syzkaller-bugs@...glegroups.com,
        tiwai@...e.de
Subject: memory leak in ath9k_hif_usb_firmware_cb

Hello,

syzbot found the following issue on:

HEAD commit:    407ab579 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=134dd026500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a3f13716fa0212fd
dashboard link: https://syzkaller.appspot.com/bug?extid=6692c72009680f7c4eb2
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=163be156500000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1775d04e500000

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

BUG: memory leak
unreferenced object 0xffff888109b4dc00 (size 192):
  comm "kworker/1:2", pid 3705, jiffies 4294941906 (age 14.110s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 18 dc b4 09 81 88 ff ff  ................
  backtrace:
    [<000000006422299c>] kmalloc include/linux/slab.h:557 [inline]
    [<000000006422299c>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
    [<000000007744b258>] ath9k_hif_usb_alloc_tx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:829 [inline]
    [<000000007744b258>] ath9k_hif_usb_alloc_urbs+0x148/0x640 drivers/net/wireless/ath/ath9k/hif_usb.c:1008
    [<000000006c8e4116>] ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1102 [inline]
    [<000000006c8e4116>] ath9k_hif_usb_firmware_cb+0x88/0x1f0 drivers/net/wireless/ath/ath9k/hif_usb.c:1235
    [<00000000e5c70763>] request_firmware_work_func+0x47/0x90 drivers/base/firmware_loader/main.c:1079
    [<0000000089bbfbae>] process_one_work+0x27d/0x590 kernel/workqueue.c:2272
    [<00000000d58def96>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2418
    [<000000001b9033f3>] kthread+0x178/0x1b0 kernel/kthread.c:292
    [<000000001b3150ee>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

BUG: memory leak
unreferenced object 0xffff88810efed240 (size 192):
  comm "kworker/1:2", pid 3705, jiffies 4294941906 (age 14.110s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 58 d2 fe 0e 81 88 ff ff  ........X.......
  backtrace:
    [<000000006422299c>] kmalloc include/linux/slab.h:557 [inline]
    [<000000006422299c>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
    [<000000007744b258>] ath9k_hif_usb_alloc_tx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:829 [inline]
    [<000000007744b258>] ath9k_hif_usb_alloc_urbs+0x148/0x640 drivers/net/wireless/ath/ath9k/hif_usb.c:1008
    [<000000006c8e4116>] ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1102 [inline]
    [<000000006c8e4116>] ath9k_hif_usb_firmware_cb+0x88/0x1f0 drivers/net/wireless/ath/ath9k/hif_usb.c:1235
    [<00000000e5c70763>] request_firmware_work_func+0x47/0x90 drivers/base/firmware_loader/main.c:1079
    [<0000000089bbfbae>] process_one_work+0x27d/0x590 kernel/workqueue.c:2272
    [<00000000d58def96>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2418
    [<000000001b9033f3>] kthread+0x178/0x1b0 kernel/kthread.c:292
    [<000000001b3150ee>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

BUG: memory leak
unreferenced object 0xffff88810efedb40 (size 192):
  comm "kworker/1:2", pid 3705, jiffies 4294941906 (age 14.110s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 58 db fe 0e 81 88 ff ff  ........X.......
  backtrace:
    [<000000006422299c>] kmalloc include/linux/slab.h:557 [inline]
    [<000000006422299c>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
    [<000000007744b258>] ath9k_hif_usb_alloc_tx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:829 [inline]
    [<000000007744b258>] ath9k_hif_usb_alloc_urbs+0x148/0x640 drivers/net/wireless/ath/ath9k/hif_usb.c:1008
    [<000000006c8e4116>] ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1102 [inline]
    [<000000006c8e4116>] ath9k_hif_usb_firmware_cb+0x88/0x1f0 drivers/net/wireless/ath/ath9k/hif_usb.c:1235
    [<00000000e5c70763>] request_firmware_work_func+0x47/0x90 drivers/base/firmware_loader/main.c:1079
    [<0000000089bbfbae>] process_one_work+0x27d/0x590 kernel/workqueue.c:2272
    [<00000000d58def96>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2418
    [<000000001b9033f3>] kthread+0x178/0x1b0 kernel/kthread.c:292
    [<000000001b3150ee>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

BUG: memory leak
unreferenced object 0xffff88810efedf00 (size 192):
  comm "kworker/1:2", pid 3705, jiffies 4294941906 (age 14.110s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 18 df fe 0e 81 88 ff ff  ................
  backtrace:
    [<000000006422299c>] kmalloc include/linux/slab.h:557 [inline]
    [<000000006422299c>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
    [<000000007744b258>] ath9k_hif_usb_alloc_tx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:829 [inline]
    [<000000007744b258>] ath9k_hif_usb_alloc_urbs+0x148/0x640 drivers/net/wireless/ath/ath9k/hif_usb.c:1008
    [<000000006c8e4116>] ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1102 [inline]
    [<000000006c8e4116>] ath9k_hif_usb_firmware_cb+0x88/0x1f0 drivers/net/wireless/ath/ath9k/hif_usb.c:1235
    [<00000000e5c70763>] request_firmware_work_func+0x47/0x90 drivers/base/firmware_loader/main.c:1079
    [<0000000089bbfbae>] process_one_work+0x27d/0x590 kernel/workqueue.c:2272
    [<00000000d58def96>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2418
    [<000000001b9033f3>] kthread+0x178/0x1b0 kernel/kthread.c:292
    [<000000001b3150ee>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

BUG: memory leak
unreferenced object 0xffff88810efedc00 (size 192):
  comm "kworker/1:2", pid 3705, jiffies 4294941906 (age 14.110s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 18 dc fe 0e 81 88 ff ff  ................
  backtrace:
    [<000000006422299c>] kmalloc include/linux/slab.h:557 [inline]
    [<000000006422299c>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
    [<000000007744b258>] ath9k_hif_usb_alloc_tx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:829 [inline]
    [<000000007744b258>] ath9k_hif_usb_alloc_urbs+0x148/0x640 drivers/net/wireless/ath/ath9k/hif_usb.c:1008
    [<000000006c8e4116>] ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1102 [inline]
    [<000000006c8e4116>] ath9k_hif_usb_firmware_cb+0x88/0x1f0 drivers/net/wireless/ath/ath9k/hif_usb.c:1235
    [<00000000e5c70763>] request_firmware_work_func+0x47/0x90 drivers/base/firmware_loader/main.c:1079
    [<0000000089bbfbae>] process_one_work+0x27d/0x590 kernel/workqueue.c:2272
    [<00000000d58def96>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2418
    [<000000001b9033f3>] kthread+0x178/0x1b0 kernel/kthread.c:292
    [<000000001b3150ee>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296



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