Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2310268ybi; Thu, 20 Jun 2019 12:46:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqz0gL7fs8wYPPUbJomnvliwesjo0ddwB9wPLqBEjchkRDd/GTKIP5WPKFy/MnYxU8LTxcFQ X-Received: by 2002:a17:902:a81:: with SMTP id 1mr125563040plp.287.1561060015925; Thu, 20 Jun 2019 12:46:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561060015; cv=none; d=google.com; s=arc-20160816; b=Owo3cA40cPmk/9g5RynigQp7IVGdainhHdpQ6+LpUFnSf3mtrUREdEvqR/l4Tdf7Tu +z7QZ9/GHW7K2ybvnPy/tnxFpEewM7OcQ1FFc4nvJpPATFdGZlJ8GL0FiAD4Autll9rE TGArFal/nX5caXKyjc5pmFDtN5D3ed0ILTvlQAWhvYTuUeTsXHvXLjVctZE13/Vg7CfG gBdQN4D+T1CpCDQBLKdHi+inPdRmsvod4ZaJjj6tpoKzi7aBhjkC/jCPcXN9t7aWVo9b 4k50POKr0uFD5xFAoIxN8AAE63L5xvqTM+dTJWIIFZZjMtXR0ab5vf0OgaGk0j6AFWOg LUPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date; bh=Zb8VHc19y4eWiaQEAToACC2aMKcz22pZrGFtuw0PTuY=; b=IXG4jOLUqUy1msXq1U16tkl8q/XmFUOzbtj1Z/bMHlA24C7FSfSxHdUkJBX69SelId 4yQWzT/yoVz8hE7sAIeU/+r+VMcTVTUHWuI6/P+BwLSN+UOQqFsqNXnOHCm/bMfc9f9K SnSqG8//USnOiypq7p//2MxjSib6FwB4yXGWA68IUHv2MGj8B+yuPykw1DLDOD+zGWT6 kdhG6MsaODVFCJzkmF1O9zJy9N3OhvdIR3yBFdmk/1wt7Muu5sKGvpMmVcjdQ8JdiUFl wtAmFHaPAqRgtvs0Kw5s1wuHnmWvk/eoOLtZqiUKFbzAigk7fAxFvpvuOuqB6+fsceVv BrmQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p13si379120pgd.347.2019.06.20.12.46.40; Thu, 20 Jun 2019 12:46:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726635AbfFTTqe (ORCPT + 99 others); Thu, 20 Jun 2019 15:46:34 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:56504 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1726293AbfFTTqd (ORCPT ); Thu, 20 Jun 2019 15:46:33 -0400 Received: (qmail 2765 invoked by uid 2102); 20 Jun 2019 15:46:32 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Jun 2019 15:46:32 -0400 Date: Thu, 20 Jun 2019 15:46:32 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: syzbot cc: andreyknvl@google.com, , , , Kernel development list , USB list , , , Subject: Re: KASAN: slab-out-of-bounds Read in p54u_load_firmware_cb In-Reply-To: <000000000000f00cf1058bb7fb56@google.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 19 Jun 2019, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit: 9939f56e usb-fuzzer: main usb gadget fuzzer driver > git tree: https://github.com/google/kasan.git usb-fuzzer > console output: https://syzkaller.appspot.com/x/log.txt?x=135e29faa00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=df134eda130bb43a > dashboard link: https://syzkaller.appspot.com/bug?extid=6d237e74cdc13f036473 > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175d946ea00000 > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+6d237e74cdc13f036473@syzkaller.appspotmail.com > > usb 3-1: Direct firmware load for isl3887usb failed with error -2 > usb 3-1: Firmware not found. > ================================================================== > BUG: KASAN: slab-out-of-bounds in p54u_load_firmware_cb.cold+0x97/0x13d > drivers/net/wireless/intersil/p54/p54usb.c:936 > Read of size 8 at addr ffff8881c9cf7588 by task kworker/1:5/2759 > > CPU: 1 PID: 2759 Comm: kworker/1:5 Not tainted 5.2.0-rc5+ #11 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 01/01/2011 > Workqueue: events request_firmware_work_func > Call Trace: > __dump_stack lib/dump_stack.c:77 [inline] > dump_stack+0xca/0x13e lib/dump_stack.c:113 > print_address_description+0x67/0x231 mm/kasan/report.c:188 > __kasan_report.cold+0x1a/0x32 mm/kasan/report.c:317 > kasan_report+0xe/0x20 mm/kasan/common.c:614 > p54u_load_firmware_cb.cold+0x97/0x13d > drivers/net/wireless/intersil/p54/p54usb.c:936 > request_firmware_work_func+0x126/0x242 > drivers/base/firmware_loader/main.c:785 > process_one_work+0x905/0x1570 kernel/workqueue.c:2269 > worker_thread+0x96/0xe20 kernel/workqueue.c:2415 > kthread+0x30b/0x410 kernel/kthread.c:255 > ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 > > Allocated by task 1612: > save_stack+0x1b/0x80 mm/kasan/common.c:71 > set_track mm/kasan/common.c:79 [inline] > __kasan_kmalloc mm/kasan/common.c:489 [inline] > __kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:462 > kmalloc include/linux/slab.h:547 [inline] > syslog_print kernel/printk/printk.c:1346 [inline] > do_syslog kernel/printk/printk.c:1519 [inline] > do_syslog+0x4f4/0x12e0 kernel/printk/printk.c:1493 > kmsg_read+0x8a/0xb0 fs/proc/kmsg.c:40 > proc_reg_read+0x1c1/0x280 fs/proc/inode.c:221 > __vfs_read+0x76/0x100 fs/read_write.c:425 > vfs_read+0x18e/0x3d0 fs/read_write.c:461 > ksys_read+0x127/0x250 fs/read_write.c:587 > do_syscall_64+0xb7/0x560 arch/x86/entry/common.c:301 > entry_SYSCALL_64_after_hwframe+0x49/0xbe > > Freed by task 1612: > save_stack+0x1b/0x80 mm/kasan/common.c:71 > set_track mm/kasan/common.c:79 [inline] > __kasan_slab_free+0x130/0x180 mm/kasan/common.c:451 > slab_free_hook mm/slub.c:1421 [inline] > slab_free_freelist_hook mm/slub.c:1448 [inline] > slab_free mm/slub.c:2994 [inline] > kfree+0xd7/0x280 mm/slub.c:3949 > syslog_print kernel/printk/printk.c:1405 [inline] > do_syslog kernel/printk/printk.c:1519 [inline] > do_syslog+0xff3/0x12e0 kernel/printk/printk.c:1493 > kmsg_read+0x8a/0xb0 fs/proc/kmsg.c:40 > proc_reg_read+0x1c1/0x280 fs/proc/inode.c:221 > __vfs_read+0x76/0x100 fs/read_write.c:425 > vfs_read+0x18e/0x3d0 fs/read_write.c:461 > ksys_read+0x127/0x250 fs/read_write.c:587 > do_syscall_64+0xb7/0x560 arch/x86/entry/common.c:301 > entry_SYSCALL_64_after_hwframe+0x49/0xbe > > The buggy address belongs to the object at ffff8881c9cf7180 > which belongs to the cache kmalloc-1k of size 1024 > The buggy address is located 8 bytes to the right of > 1024-byte region [ffff8881c9cf7180, ffff8881c9cf7580) > The buggy address belongs to the page: > page:ffffea0007273d00 refcount:1 mapcount:0 mapping:ffff8881dac02a00 > index:0x0 compound_mapcount: 0 > flags: 0x200000000010200(slab|head) > raw: 0200000000010200 dead000000000100 dead000000000200 ffff8881dac02a00 > raw: 0000000000000000 00000000000e000e 00000001ffffffff 0000000000000000 > page dumped because: kasan: bad access detected > > Memory state around the buggy address: > ffff8881c9cf7480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff8881c9cf7500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > > ffff8881c9cf7580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc > ^ > ffff8881c9cf7600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff8881c9cf7680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ================================================================== Isn't this the same as syzkaller bug 200d4bb11b23d929335f ? Doesn't the same patch fix it? Alan Stern