Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4457526pxv; Tue, 29 Jun 2021 07:29:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzlNW1oUIKiKL6IIuQ4V4rZ9+kScRGaU5uYR4VGdrVizVFqcUu35Mw1Ycnied7QQJFPQ25g X-Received: by 2002:aa7:d309:: with SMTP id p9mr40697109edq.340.1624976965660; Tue, 29 Jun 2021 07:29:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624976965; cv=none; d=google.com; s=arc-20160816; b=FyYILv2Ev7saN7dGZzuTZEU3O1Bwws0TRIzhsu2JIMEMyqfNNrbYj5P+sOrp8n3mQ+ +I3KnxUH8ci2IZQhlTBQZzNkqtgikNFyl5iDnk4QuAOSya4m2DAQ9eQ6JBfmFfMSmZBr Eu3G7Yu8a4NnpAVGp9bq1TKFtd/9sy4Jzh9xhIBO5EfDQJtDWbycRZPSytzicDLZPDJL FieReLRhvzmIoQ13Usb4+oATbabTNId6QVDrk7dUVHtCWcQi2j7AlD2GvifJ0SYHmucM 3WxXSBo/tt4tV28NQ152mlsQlRxcNWvWP+KMF3VZhawg929w92ajgN1i4WEWEqwA8Me4 5n9A== 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:message-id:date:subject:cc:to:from; bh=/2CMctJFUCUk5kRtnF6fkab3mKRIqUvdqBouBgocxhU=; b=EzlKM6iZCwuA/jaDP7wic+YxL4LShSNPUjt7ohmNoQhxXH8ylTG6wbz5DTO6+xW1cL G3A4rTsmcZoe+cBHBWPKKnmKv/9DTsRabcNyYKjf/RSo3YKHkroL+ObBurcRh0188o33 hs9XLCtqlABo/uX883c/AnQyh+2Z4PP37IApDSTRRZirNlyF6r2c9d4HYiew5RqdT7xM DmUw7pnqBEzxqktBUiI7/kp+Qg1wNjOJCd/wWtFO/OL4YBVnYCauDRcd4ZiSIYxJSubH h+xLZ+deaNMAHhGLgaaXalufnxTANL8hNt3BVzTROAjlWJnsSNJ7F7lcK3QawCkp7kcQ Pt+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w24si1843536eds.438.2021.06.29.07.29.02; Tue, 29 Jun 2021 07:29:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234311AbhF2O37 (ORCPT + 99 others); Tue, 29 Jun 2021 10:29:59 -0400 Received: from szxga03-in.huawei.com ([45.249.212.189]:9319 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231194AbhF2O3x (ORCPT ); Tue, 29 Jun 2021 10:29:53 -0400 Received: from dggeme754-chm.china.huawei.com (unknown [172.30.72.53]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4GDmsp2r3Fz73xx; Tue, 29 Jun 2021 22:23:10 +0800 (CST) Received: from huawei.com (10.175.127.227) by dggeme754-chm.china.huawei.com (10.3.19.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Tue, 29 Jun 2021 22:27:23 +0800 From: Ye Bin To: , , , , CC: Ye Bin Subject: [PATCH 1/2] ext4: Fix use-after-free about sbi->s_mmp_tsk Date: Tue, 29 Jun 2021 22:36:02 +0800 Message-ID: <20210629143603.2166962-2-yebin10@huawei.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210629143603.2166962-1-yebin10@huawei.com> References: <20210629143603.2166962-1-yebin10@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.175.127.227] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggeme754-chm.china.huawei.com (10.3.19.100) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org After merge 618f003199c6("ext4: fix memory leak in ext4_fill_super") commit, we add delay in ext4_remount after "sb->s_flags |= SB_RDONLY", then remount filesystem with read-only kasan report following warning: [ 888.695326] ================================================================== [ 888.696566] BUG: KASAN: use-after-free in kthread_stop+0x4c/0x2f0 [ 888.697599] Write of size 4 at addr ffff8883849e0020 by task mount/2013 [ 888.698707] [ 888.698982] CPU: 4 PID: 2013 Comm: mount Not tainted 4.19.95-00013-ga369a6189bbf-dirty #413 [ 888.700376] Hardware name: QEMU Standard PC [ 888.702587] Call Trace: [ 888.703017] dump_stack+0x108/0x15f [ 888.703615] print_address_description+0xa5/0x372 [ 888.704420] kasan_report.cold+0x236/0x2a8 [ 888.705761] check_memory_region+0x240/0x270 [ 888.706486] kasan_check_write+0x20/0x30 [ 888.707156] kthread_stop+0x4c/0x2f0 [ 888.707776] ext4_stop_mmpd+0x32/0x90 [ 888.708262] ext4_remount.cold+0xf6/0x116 [ 888.712671] do_remount_sb+0xff/0x460 [ 888.714007] do_mount+0xce3/0x1be0 [ 888.717749] ksys_mount+0xb2/0x150 [ 888.718163] __x64_sys_mount+0x6a/0x80 [ 888.718607] do_syscall_64+0xd9/0x1f0 [ 888.719047] entry_SYSCALL_64_after_hwframe+0x44/0xa9 As kmmpd will exit if filesystem is read-only. Then sbi->s_mmp_tsk become wild ptr, lead to use-after-free. As kmmpd will exit by others(call ktread_stop) or by itself. After 618f003199c6 commit we can trigger this issue very easy. Before this commit also exist this issue. If kmmpd exit by itself, after merge 618f003199c6 commit there will trigger UAF when umount filesystem. To fix this issue, introduce sbi->s_mmp_lock to protect sbi->s_mmp_tsk. If kmmpd exit by itself, we set sbi->s_mmp_tsk with NULL, and release mmp buffer_head. Fixes: 618f003199c6 ("ext4: fix memory leak in ext4_fill_super") Signed-off-by: Ye Bin --- fs/ext4/ext4.h | 1 + fs/ext4/mmp.c | 24 ++++++++++++++++++++++-- fs/ext4/super.c | 1 + 3 files changed, 24 insertions(+), 2 deletions(-) diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index 8d3446746718..a479da37fed4 100644 --- a/fs/ext4/ext4.h +++ b/fs/ext4/ext4.h @@ -1489,6 +1489,7 @@ struct ext4_sb_info { struct completion s_kobj_unregister; struct super_block *s_sb; struct buffer_head *s_mmp_bh; + struct mutex s_mmp_lock; /* Journaling */ struct journal_s *s_journal; diff --git a/fs/ext4/mmp.c b/fs/ext4/mmp.c index 6cb598b549ca..fc18a8c205c7 100644 --- a/fs/ext4/mmp.c +++ b/fs/ext4/mmp.c @@ -128,8 +128,9 @@ void __dump_mmp_msg(struct super_block *sb, struct mmp_struct *mmp, static int kmmpd(void *data) { struct super_block *sb = (struct super_block *) data; - struct ext4_super_block *es = EXT4_SB(sb)->s_es; - struct buffer_head *bh = EXT4_SB(sb)->s_mmp_bh; + struct ext4_sb_info *sbi = EXT4_SB(sb); + struct ext4_super_block *es = sbi->s_es; + struct buffer_head *bh = sbi->s_mmp_bh; struct mmp_struct *mmp; ext4_fsblk_t mmp_block; u32 seq = 0; @@ -245,16 +246,35 @@ static int kmmpd(void *data) retval = write_mmp_block(sb, bh); exit_thread: + /* + * Maybe s_mmp_tsk kthread is stoped by others or by itself. If exit + * by itself then sbi->s_mmp_tsk will be wild ptr, so there is need + * set sbi->s_mmp_tsk with NULL, and also release mmp buffer_head. + */ + while (!kthread_should_stop()) { + if (!mutex_trylock(&sbi->s_mmp_lock)) + continue; + + if (sbi->s_mmp_tsk) { + sbi->s_mmp_tsk = NULL; + brelse(bh); + } + mutex_unlock(&sbi->s_mmp_lock); + break; + } + return retval; } void ext4_stop_mmpd(struct ext4_sb_info *sbi) { + mutex_lock(&sbi->s_mmp_lock); if (sbi->s_mmp_tsk) { kthread_stop(sbi->s_mmp_tsk); brelse(sbi->s_mmp_bh); sbi->s_mmp_tsk = NULL; } + mutex_unlock(&sbi->s_mmp_lock); } /* diff --git a/fs/ext4/super.c b/fs/ext4/super.c index c3942804b57f..5bc3230553fb 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -4786,6 +4786,7 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent) needs_recovery = (es->s_last_orphan != 0 || ext4_has_feature_journal_needs_recovery(sb)); + mutex_init(&sbi->s_mmp_lock); if (ext4_has_feature_mmp(sb) && !sb_rdonly(sb)) if (ext4_multi_mount_protect(sb, le64_to_cpu(es->s_mmp_block))) goto failed_mount3a; -- 2.31.1