From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38AB5C46467 for ; Mon, 28 Nov 2022 10:15:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230045AbiK1KPY (ORCPT ); Mon, 28 Nov 2022 05:15:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229743AbiK1KPV (ORCPT ); Mon, 28 Nov 2022 05:15:21 -0500 Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 44861140A6 for ; Mon, 28 Nov 2022 02:15:19 -0800 (PST) Received: by mail-lj1-x22d.google.com with SMTP id r8so12542674ljn.8 for ; Mon, 28 Nov 2022 02:15:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=REXAMmbN1XbT9DHnD6TPE5PXHyaAuL1DAIE2Het67no=; b=GR70uuge98m9/9SRWUb6ISLek6m7vM8eiVbENjhswTlJTWOkSqLnMTpdYGKFRgc5DR GhwJoS4aoir+j7RKShgIXWEG4ZAz8VrDXCRIAWgcAZ2SQPlMFeW3zYbo+YRG8I++AOze TO23cWNyumr65ABa80S41GjE0Bv8vPf0X8UrYBl5ESMrUhIwTi5wxF9HP6IKdQMtB9dR v5D5uagnS2IIu2OkQitd6KGCVMIBNu/tjJJaKfEFSsk4GZ1wuBKfylItAKHdduUk0lFg 2f8LIoLYQ0BjLF+RmtKKELORV+9hQDB3sLFbV1qRbFYO43GPzeeaLJCKdEeaQrT3nSxj QTug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=REXAMmbN1XbT9DHnD6TPE5PXHyaAuL1DAIE2Het67no=; b=xWwtWo5arWya1q1QSm27DTStDogZCF5DsGGLY5xJF9FA+OW/8bXiZ21B+KUsJSU8ib 7fuZk3STPEtU3wI3a307JZqil3DazNV6QnIX+7jp9SJU+F0TA8YmV5yWGackQAjkrzB8 cOG1AGb1u4nrxGg+Ysmzq9RJxHiPDKdCPcXgTo4iq81mMM6hU2BQBHvcdmKFbE8GqxAv sXqgUiqUajHBM9yAoMxemZ0PEVyyO8HcRyF0f2EaIF3RgJY8EJmGnrrG0Vs620pA/WQf 34Ls3exghQvqdTU+tOkDWezzAVKm+KJZqD2qTswaYo2xUWx1/jyAZcyhB2slFnCLcY4R y0Kw== X-Gm-Message-State: ANoB5pm7CawRtVYOQ3kDpSWF7WUxXTrhvnpAAEUv5gbqoJimEl696IHZ epDo1Z/jzhQ3kl/N3tbepMy5zQ== X-Google-Smtp-Source: AA0mqf6qD2lEOKBHo+tS8NZgUJSwxk7ZWROD0YU4bbwFemDyRR1wPPIXIknoKsrrNxgbH/LLRjG+Wg== X-Received: by 2002:a2e:9b43:0:b0:279:80bb:9e49 with SMTP id o3-20020a2e9b43000000b0027980bb9e49mr7154045ljj.355.1669630518211; Mon, 28 Nov 2022 02:15:18 -0800 (PST) Received: from [192.168.0.20] (088156142067.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.67]) by smtp.gmail.com with ESMTPSA id z4-20020a05651c11c400b0027998486803sm749127ljo.130.2022.11.28.02.15.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Nov 2022 02:15:17 -0800 (PST) Message-ID: <1a6abe2b-c382-a283-74a0-5869d2ba102e@linaro.org> Date: Mon, 28 Nov 2022 11:15:16 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [syzbot] KASAN: use-after-free Read in rfkill_blocked Content-Language: en-US To: Dmitry Vyukov Cc: Johannes Berg , syzbot , davem@davemloft.net, edumazet@google.com, kuba@kernel.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com References: <000000000000790da005ee3175a8@google.com> <26b9771db88198ff982476e3e24f411277cd213b.camel@sipsolutions.net> <0ee688ac-5c34-1592-23d3-fe100cadc570@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/11/2022 11:07, Dmitry Vyukov wrote: > On Sun, 27 Nov 2022 at 20:59, Krzysztof Kozlowski > wrote: >> >> On 25/11/2022 10:09, Johannes Berg wrote: >>> Looks like an NFC issue to me, Krzysztof? >>> >>> I mean, rfkill got allocated by nfc_register_device(), freed by >>> nfc_unregister_device(), and then used by nfc_dev_up(). Seems like the >>> last bit shouldn't be possible after nfc_unregister_device()? >>> >>> johannes >>> >>> On Wed, 2022-11-23 at 22:24 -0800, syzbot wrote: >>>> Hello, >>>> >>>> syzbot found the following issue on: >>>> >>>> HEAD commit: 0966d385830d riscv: Fix auipc+jalr relocation range checks >>>> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes >>>> console output: https://syzkaller.appspot.com/x/log.txt?x=11196d0d880000 >>>> kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921 >>>> dashboard link: https://syzkaller.appspot.com/bug?extid=0299462c067009827b2a >>>> compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 >>>> userspace arch: riscv64 >>>> >>>> Unfortunately, I don't have any reproducer for this issue yet. >>>> >>>> IMPORTANT: if you fix the issue, please add the following tag to the commit: >>>> Reported-by: syzbot+0299462c067009827b2a@syzkaller.appspotmail.com >>>> >>>> ================================================================== >>>> BUG: KASAN: use-after-free in __lock_acquire+0x8ee/0x333e kernel/locking/lockdep.c:4897 >>>> Read of size 8 at addr ffffaf8024249018 by task syz-executor.0/7946 >>>> >>>> CPU: 0 PID: 7946 Comm: syz-executor.0 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 >>>> Hardware name: riscv-virtio,qemu (DT) >>>> Call Trace: >>>> [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 >>>> [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 >>>> [] __dump_stack lib/dump_stack.c:88 [inline] >>>> [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 >>>> [] print_address_description.constprop.0+0x2a/0x330 mm/kasan/report.c:255 >>>> [] __kasan_report mm/kasan/report.c:442 [inline] >>>> [] kasan_report+0x184/0x1e0 mm/kasan/report.c:459 >>>> [] check_region_inline mm/kasan/generic.c:183 [inline] >>>> [] __asan_load8+0x6e/0x96 mm/kasan/generic.c:256 >>>> [] __lock_acquire+0x8ee/0x333e kernel/locking/lockdep.c:4897 >>>> [] lock_acquire.part.0+0x1d0/0x424 kernel/locking/lockdep.c:5639 >>>> [] lock_acquire+0x54/0x6a kernel/locking/lockdep.c:5612 >>>> [] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] >>>> [] _raw_spin_lock_irqsave+0x3e/0x62 kernel/locking/spinlock.c:162 >>>> [] rfkill_blocked+0x22/0x62 net/rfkill/core.c:941 >>>> [] nfc_dev_up+0x8e/0x26c net/nfc/core.c:102 >>>> [] nfc_genl_dev_up+0x5e/0x8a net/nfc/netlink.c:770 >>>> [] genl_family_rcv_msg_doit+0x19a/0x23c net/netlink/genetlink.c:731 >>>> [] genl_family_rcv_msg net/netlink/genetlink.c:775 [inline] >>>> [] genl_rcv_msg+0x236/0x3ba net/netlink/genetlink.c:792 >>>> [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 >>>> [] genl_rcv+0x36/0x4c net/netlink/genetlink.c:803 >>>> [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] >>>> [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 >>>> [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 >>>> [] sock_sendmsg_nosec net/socket.c:705 [inline] >>>> [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 >>>> [] ____sys_sendmsg+0x46e/0x484 net/socket.c:2413 >>>> [] ___sys_sendmsg+0x16c/0x1f6 net/socket.c:2467 >>>> [] __sys_sendmsg+0xba/0x150 net/socket.c:2496 >>>> [] __do_sys_sendmsg net/socket.c:2505 [inline] >>>> [] sys_sendmsg+0x2c/0x3a net/socket.c:2503 >>>> [] ret_from_syscall+0x0/0x2 >>>> >>>> Allocated by task 7946: >>>> stack_trace_save+0xa6/0xd8 kernel/stacktrace.c:122 >>>> kasan_save_stack+0x2c/0x58 mm/kasan/common.c:38 >>>> kasan_set_track mm/kasan/common.c:45 [inline] >>>> set_alloc_info mm/kasan/common.c:436 [inline] >>>> ____kasan_kmalloc mm/kasan/common.c:515 [inline] >>>> ____kasan_kmalloc mm/kasan/common.c:474 [inline] >>>> __kasan_kmalloc+0x80/0xb2 mm/kasan/common.c:524 >>>> kasan_kmalloc include/linux/kasan.h:270 [inline] >>>> __kmalloc+0x190/0x318 mm/slub.c:4424 >>>> kmalloc include/linux/slab.h:586 [inline] >>>> kzalloc include/linux/slab.h:715 [inline] >>>> rfkill_alloc+0x96/0x1aa net/rfkill/core.c:983 >>>> nfc_register_device+0xe4/0x29e net/nfc/core.c:1129 >>>> nci_register_device+0x538/0x612 net/nfc/nci/core.c:1252 >>>> virtual_ncidev_open+0x82/0x12c drivers/nfc/virtual_ncidev.c:143 >>>> misc_open+0x272/0x2c8 drivers/char/misc.c:141 >>>> chrdev_open+0x1d4/0x478 fs/char_dev.c:414 >>>> do_dentry_open+0x2a4/0x7d4 fs/open.c:824 >>>> vfs_open+0x52/0x5e fs/open.c:959 >>>> do_open fs/namei.c:3476 [inline] >>>> path_openat+0x12b6/0x189e fs/namei.c:3609 >>>> do_filp_open+0x10e/0x22a fs/namei.c:3636 >>>> do_sys_openat2+0x174/0x31e fs/open.c:1214 >>>> do_sys_open fs/open.c:1230 [inline] >>>> __do_sys_openat fs/open.c:1246 [inline] >>>> sys_openat+0xdc/0x164 fs/open.c:1241 >>>> ret_from_syscall+0x0/0x2 >>>> >>>> Freed by task 7944: >>>> stack_trace_save+0xa6/0xd8 kernel/stacktrace.c:122 >>>> kasan_save_stack+0x2c/0x58 mm/kasan/common.c:38 >>>> kasan_set_track+0x1a/0x26 mm/kasan/common.c:45 >>>> kasan_set_free_info+0x1e/0x3a mm/kasan/generic.c:370 >>>> ____kasan_slab_free mm/kasan/common.c:366 [inline] >>>> ____kasan_slab_free+0x15e/0x180 mm/kasan/common.c:328 >>>> __kasan_slab_free+0x10/0x18 mm/kasan/common.c:374 >>>> kasan_slab_free include/linux/kasan.h:236 [inline] >>>> slab_free_hook mm/slub.c:1728 [inline] >>>> slab_free_freelist_hook+0x8e/0x1cc mm/slub.c:1754 >>>> slab_free mm/slub.c:3509 [inline] >>>> kfree+0xe0/0x3e4 mm/slub.c:4562 >>>> rfkill_release+0x20/0x2a net/rfkill/core.c:831 >>>> device_release+0x66/0x148 drivers/base/core.c:2229 >>>> kobject_cleanup lib/kobject.c:705 [inline] >>>> kobject_release lib/kobject.c:736 [inline] >>>> kref_put include/linux/kref.h:65 [inline] >>>> kobject_put+0x1bc/0x38e lib/kobject.c:753 >>>> put_device+0x28/0x3a drivers/base/core.c:3512 >>>> rfkill_destroy+0x2a/0x3c net/rfkill/core.c:1142 >>>> nfc_unregister_device+0xac/0x232 net/nfc/core.c:1167 >>>> nci_unregister_device+0x168/0x182 net/nfc/nci/core.c:1298 >>>> virtual_ncidev_close+0x9c/0xbc drivers/nfc/virtual_ncidev.c:163 >> >> There were several issues found recently in virtual NCI driver, so this >> might be one of them. There is no reproducer, though... > > > Hi Krzysztof, > > Do you think it's related specifically to the virtual driver? Both, although maybe not this particular issue. There were like five separate reports last few days... > > I would assume it's a bug in the NCI core itself related to dynamic > device destructions. This should affect e.g. USB devices as well. Earlier this year there was a bigger fix for unregister path in NFC - see commits: da5c0f119203 (nfc_unregister_device+nfc_fw_download ef27324e2c (nci_unregister_device+nci_cmd_work) 1b0e81416 (rfkill related) and these pointed out inherent issues in locking/synchronization of NFC core modules. I don't think we fixed all of the core issues, rather only what was reported, so some specific scenarios. > It's an issue only in the virtual driver. It means that the virtual > driver uses the NCI core incorrectly, not the way all real drivers use > it. If so the question is: what is the difference? We need to fix it. > It's not useful to have unrealistic test drivers -- we both get false > positives and don't get true positives. > > I think the issue may be localized from the KASAN report itself w/o a > reproducer. > Is there proper synchronization between > nfc_unregister_device/rfkill_destroy and nfc_dev_up/rfkill_blocked? > Something that prevents rfkill_blocked to be called after > rfkill_destroy? If not, then that's the issue. Mentioned 1b0e81416a tried to do this and that time I had impression fix is correct. However it seems it is not... (or not enough) Best regards, Krzysztof