Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp7649599rwb; Wed, 23 Nov 2022 09:03:10 -0800 (PST) X-Google-Smtp-Source: AA0mqf4mmfrOZfKeOLJqQ+esaN83cZcn9h4Perfw12AC9ppMZeGKGsY9NXz771Irb0uqeGmGNFA+ X-Received: by 2002:a17:906:4e8c:b0:7ba:9c18:1204 with SMTP id v12-20020a1709064e8c00b007ba9c181204mr1343820eju.262.1669222989789; Wed, 23 Nov 2022 09:03:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669222989; cv=none; d=google.com; s=arc-20160816; b=nnfN5+IQd6jvxIFOnc5GyNMiDsraC9fqdyABCkjL0qUlLLisNeP0G39atZ2PKS7URI ujxJ5cNLCYOlIQsSkVah0LlQcdB0n8dAgakBum2OLDw+g5ecp4OdA3ZoGUH6ARiKD+p9 r+lhJ0chBThZ/EAd3f/YDYKkxCtEh+9NKxNHPYt5FJQ1D5WkY6r8cyT3ZQdwefvHaGuy gL4y0V9ikFjhbeN1e4cph2EbIULRH2eRmLGL1z6yclLOiYgjl2H17zJCdevjDBctd/jB o0PICzthrKiU4AuHmPaVSeCYTG2rsru7IU5sWlXHS9o9pKHNdOfjheFwoLWih4TJUQlc au5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :dkim-signature; bh=Mo9Cu02IrQqnqkR8eRuBSSZhf6FA5DQgEMy2KAnXWBA=; b=IAxD3EE/cfjvt69S/qcXnoptPInXBw59MLiYsc1nixfv0wXz7oKWeWpHNmqFU5FIpS IGSrJIlNxH/QsSOY1mZntEH8LXNGQH6EbInLKlt1H7RDHeHjQaEqe0esNsA7wE05zqsl 79MFoMqxLMJgPi1IDrzAEBeT2K2GUE2hLTz9RYI6Ad41RqiU56XM+fYO6Vvw0aXP5zGe lPFnyl5d1PkLq6jG0sRIb+FEtgdYNFzt7h2MaSxvHoVv4BnPdLPtaVpA5gmboiRbjCx3 1I3kZiTlYl+0B0qT5z/f7wXyt+jXeT6AwOQKSkVAtwQncyp+K6VdkNgQbZqdvHynGNfq FWfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ojkt020h; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y18-20020a056402359200b00462e23be64fsi378605edc.578.2022.11.23.09.02.41; Wed, 23 Nov 2022 09:03:09 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ojkt020h; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238810AbiKWQJi (ORCPT + 88 others); Wed, 23 Nov 2022 11:09:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238779AbiKWQJg (ORCPT ); Wed, 23 Nov 2022 11:09:36 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5EA8FC689A for ; Wed, 23 Nov 2022 08:08:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669219721; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Mo9Cu02IrQqnqkR8eRuBSSZhf6FA5DQgEMy2KAnXWBA=; b=Ojkt020h0Q5ua9C6TY15rvSjysBTZfnL7fqc48SE/eJNzTMgQogGCB1McTg4jA4xT/Ffgs jpjoq+/SHBtb1Ouh6PbtxVy3TYlhAT7m5uEJMCDQ6Sm/e+TASZM4SrOTv2uBw1PUj73c4l 4q1GGO1CRFH8EcRydRSzy3WaSO9r7fU= Received: from mail-pl1-f197.google.com (mail-pl1-f197.google.com [209.85.214.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-333-A6nkcRe3P_6YQLdzbqDzpw-1; Wed, 23 Nov 2022 11:08:39 -0500 X-MC-Unique: A6nkcRe3P_6YQLdzbqDzpw-1 Received: by mail-pl1-f197.google.com with SMTP id j16-20020a170902da9000b001893d5da3acso2284181plx.23 for ; Wed, 23 Nov 2022 08:08:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to:from :subject:cc:to:message-id:date:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=Mo9Cu02IrQqnqkR8eRuBSSZhf6FA5DQgEMy2KAnXWBA=; b=nizWh2tc8OqyLMYxPuXMfWQpPHyqCmXJXiE4WnM/zOUjB2TetFr2Fh/QF8oPhQ5jhp fcREks68ud2znBeXh79h+W481wdUL37wBvlb5uxD2AWoKmeETS+hSxzuFE/zcurqRA6Y FC/3Or0JTh5aKoz1x9UCbafoyHQ5TvSic6540P+IOo9E8q40vqcGozJ0zwDQkPKQTDqd mKbLe3tCJnsrx8yU19ktfx5VbNbRzRkoslzyd5aC/jUNv3Co4/KQTG/IO+kZ3etrnGw9 ZY2HZuh58/rLIBH8FkdGfFAHTCCQIfWUYqnlRGB3MHOcjTTBlw4sf2yptH9PqdLeyoAF uRdw== X-Gm-Message-State: ANoB5pl6Xe5fk6eRNYraWTTuY2kPTsYI8Vi3ErSv/Ix/P2C8yfW64zC4 +CkeKSclrUsEeHYViAwwlk7jmSxY4VFJy3mcEF733dX/D76WWGp/jfO3wSyvDQu5EfV27T7Kg7H 2Czf2iOkwQlFJjkXho0OAklC4 X-Received: by 2002:a17:902:cf4b:b0:186:7a1d:b6ee with SMTP id e11-20020a170902cf4b00b001867a1db6eemr14339705plg.67.1669219716643; Wed, 23 Nov 2022 08:08:36 -0800 (PST) X-Received: by 2002:a17:902:cf4b:b0:186:7a1d:b6ee with SMTP id e11-20020a170902cf4b00b001867a1db6eemr14339673plg.67.1669219716324; Wed, 23 Nov 2022 08:08:36 -0800 (PST) Received: from localhost ([240d:1a:c0d:9f00:4f2f:926a:23dd:8588]) by smtp.gmail.com with ESMTPSA id n5-20020a170902e54500b001893e8ffa34sm2237343plf.97.2022.11.23.08.08.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Nov 2022 08:08:35 -0800 (PST) Date: Thu, 24 Nov 2022 01:08:31 +0900 (JST) Message-Id: <20221124.010831.156785940884442572.syoshida@redhat.com> To: jasowang@redhat.com Cc: edumazet@google.com, davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, syzbot+106f9b687cd64ee70cd1@syzkaller.appspotmail.com Subject: Re: [PATCH v2] net: tun: Fix use-after-free in tun_detach() From: Shigeru Yoshida In-Reply-To: <88643033-45e1-3078-cb41-d7255ef874ad@redhat.com> References: <20221123.031005.476714651315933198.syoshida@redhat.com> <88643033-45e1-3078-cb41-d7255ef874ad@redhat.com> X-Mailer: Mew version 6.8 on Emacs 28.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jason, On Wed, 23 Nov 2022 12:20:47 +0800, Jason Wang wrote: > > 在 2022/11/23 02:47, Eric Dumazet 写道: >> On Tue, Nov 22, 2022 at 10:10 AM Shigeru Yoshida >> wrote: >>> Hi Eric, >>> >>> On Mon, 21 Nov 2022 08:47:17 -0800, Eric Dumazet wrote: >>>> On Sun, Nov 20, 2022 at 1:02 AM Shigeru Yoshida >>>> wrote: >>>>> syzbot reported use-after-free in tun_detach() [1]. This causes call >>>>> trace like below: >>>>> >>>>> ================================================================== >>>>> BUG: KASAN: use-after-free in notifier_call_chain+0x1ee/0x200 >>>>> kernel/notifier.c:75 >>>>> Read of size 8 at addr ffff88807324e2a8 by task syz-executor.0/3673 >>>>> >>>>> CPU: 0 PID: 3673 Comm: syz-executor.0 Not tainted >>>>> 6.1.0-rc5-syzkaller-00044-gcc675d22e422 #0 >>>>> Hardware name: Google Google Compute Engine/Google Compute Engine, >>>>> BIOS Google 10/26/2022 >>>>> Call Trace: >>>>> >>>>> __dump_stack lib/dump_stack.c:88 [inline] >>>>> dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 >>>>> print_address_description mm/kasan/report.c:284 [inline] >>>>> print_report+0x15e/0x461 mm/kasan/report.c:395 >>>>> kasan_report+0xbf/0x1f0 mm/kasan/report.c:495 >>>>> notifier_call_chain+0x1ee/0x200 kernel/notifier.c:75 >>>>> call_netdevice_notifiers_info+0x86/0x130 net/core/dev.c:1942 >>>>> call_netdevice_notifiers_extack net/core/dev.c:1983 [inline] >>>>> call_netdevice_notifiers net/core/dev.c:1997 [inline] >>>>> netdev_wait_allrefs_any net/core/dev.c:10237 [inline] >>>>> netdev_run_todo+0xbc6/0x1100 net/core/dev.c:10351 >>>>> tun_detach drivers/net/tun.c:704 [inline] >>>>> tun_chr_close+0xe4/0x190 drivers/net/tun.c:3467 >>>>> __fput+0x27c/0xa90 fs/file_table.c:320 >>>>> task_work_run+0x16f/0x270 kernel/task_work.c:179 >>>>> exit_task_work include/linux/task_work.h:38 [inline] >>>>> do_exit+0xb3d/0x2a30 kernel/exit.c:820 >>>>> do_group_exit+0xd4/0x2a0 kernel/exit.c:950 >>>>> get_signal+0x21b1/0x2440 kernel/signal.c:2858 >>>>> arch_do_signal_or_restart+0x86/0x2300 arch/x86/kernel/signal.c:869 >>>>> exit_to_user_mode_loop kernel/entry/common.c:168 [inline] >>>>> exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203 >>>>> __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] >>>>> syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296 >>>>> do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86 >>>>> entry_SYSCALL_64_after_hwframe+0x63/0xcd >>>>> >>>>> The cause of the issue is that sock_put() from __tun_detach() drops >>>>> last reference count for struct net, and then notifier_call_chain() >>>>> from netdev_state_change() accesses that struct net. >>>>> >>>>> This patch fixes the issue by calling sock_put() from tun_detach() >>>>> after all necessary accesses for the struct net has done. >>>>> >>>>> Fixes: 83c1f36f9880 ("tun: send netlink notification when the device >>>>> is modified") >>>>> Reported-by: syzbot+106f9b687cd64ee70cd1@syzkaller.appspotmail.com >>>>> Link: >>>>> https://syzkaller.appspot.com/bug?id=96eb7f1ce75ef933697f24eeab928c4a716edefe >>>>> [1] >>>>> Signed-off-by: Shigeru Yoshida >>>>> --- >>>>> v2: >>>>> - Include symbolic stack trace >>>>> - Add Fixes and Reported-by tags >>>>> v1: >>>>> https://lore.kernel.org/all/20221119075615.723290-1-syoshida@redhat.com/ >>>>> --- >>>>> drivers/net/tun.c | 6 +++++- >>>>> 1 file changed, 5 insertions(+), 1 deletion(-) >>>>> >>>>> diff --git a/drivers/net/tun.c b/drivers/net/tun.c >>>>> index 7a3ab3427369..ce9fcf4c8ef4 100644 >>>>> --- a/drivers/net/tun.c >>>>> +++ b/drivers/net/tun.c >>>>> @@ -686,7 +686,6 @@ static void __tun_detach(struct tun_file *tfile, >>>>> bool clean) >>>>> if (tun) >>>>> xdp_rxq_info_unreg(&tfile->xdp_rxq); >>>>> ptr_ring_cleanup(&tfile->tx_ring, tun_ptr_free); >>>>> - sock_put(&tfile->sk); >>>>> } >>>>> } >>>>> >>>>> @@ -702,6 +701,11 @@ static void tun_detach(struct tun_file *tfile, >>>>> bool clean) >>>>> if (dev) >>>>> netdev_state_change(dev); >>>>> rtnl_unlock(); >>>>> + >>>>> + if (clean) { >>>> Would you mind explaining (a comment would be nice) why this barrier >>>> is needed ? >>> I thought that tfile is accessed with rcu_lock(), so I put >>> synchronize_rcu() here. Please let me know if I misunderstand the >>> concept of rcu (I'm losing my confidence...). >>> >> Addin Jason for comments. >> >> If an RCU grace period was needed before commit 83c1f36f9880 ("tun: >> send netlink notification when the device is modified"), >> would we need another patch ? > > > I think we don't need another synchronization here. __tun_detach() has > already done the necessary synchronization when it tries to modify > tun->tfiles array and tfile->tun. Thank you so much for your comment. I'll prepare v3 patch to remove calling synchronize_rcu(). Thanks, Shigeru > Thanks > > >> >> Also sock_flag(sk, SOCK_RCU_FREE) would probably be better than adding >> a synchronize_rcu() (if again a grace period is needed) >> >> >> >>> Thanks, >>> Shigeru >>> >>>> Thanks. >>>> >>>>> + synchronize_rcu(); >>>>> + sock_put(&tfile->sk); >>>>> + } >>>>> } >>>>> >>>>> static void tun_detach_all(struct net_device *dev) >>>>> -- >>>>> 2.38.1 >>>>> >