Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp1822563rwb; Fri, 12 Aug 2022 07:24:09 -0700 (PDT) X-Google-Smtp-Source: AA6agR5esKTfvqHW/BG8wgaQKIc4DcglVbV9xxXFnz+Yas9KAfkz8WDQI0D3pbh/HWlRMurm19CK X-Received: by 2002:a17:903:18a:b0:16f:8a63:18fe with SMTP id z10-20020a170903018a00b0016f8a6318femr4297507plg.174.1660314249591; Fri, 12 Aug 2022 07:24:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660314249; cv=none; d=google.com; s=arc-20160816; b=VrI/rXCJMNjwl9U9JYbSh/MietVHaZRp4evyikXYo8RWSMbAT9NSmjzAFGEFR3qv+k xZUopeX2FGRCjgA3BvGixWVBo4ZMKmbPcl/oLRKVBedk8krpteW3X9R9NX/YH16Hy75s xYGjXCtVxCxB4IGIbjQ6u5XMu7nL6CJvB4rreNLmlfxYMcj3sSJRO8F7fx/Mjmc+XRN6 oEMh1gZBjPo1feMyZoWtidZ3SEeRfYKQjz4REWYJKCUT5ckxtqJRbA/hWjFTIu65sLRw b06SYwh/BndGNpf/43eZ5kqZp1+4i92wZOeT4fG2i5rwJNrIt8+SBdTRLRC4UZsVzr12 Tsrg== 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 :message-id:date:subject:cc:to:from:dkim-signature:dkim-signature; bh=orx0gU5XjtXTeLL+wu1bGYrutnbNzbrK9E3FTi+mTho=; b=QFRFFO0S9+Gdd0I/B1uh3TlJ/kJ51x5Z3Z40xFuJ1KSh9IqOpbzshz4fhg7f2wj0dQ x+cQP5/tsa0TigVQc7PQYivNWGFap4ic7N/4G4MczylmhKbMDK1PH55Ipjh6cupNNqy9 VkiKU64aB/XGnbEi149EwOSwXAUVdSLE4y9d8CN5u0ZVT3rbHaOTvNSc25YK1TBlxvYW n6TgN8PfmYEnZGF/KN/O345MJImY7vlNM7tQW0lwj9oTo4g04dN/0GHsrCNmnA5yVg5r d21Jn84O7g1Sk9qU1yyTC/O1kfyiILpcmiIGC5Hb498pGpw7ghNOC1GwU0LUuMKZlMjP XeZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b="UyM/sksT"; dkim=neutral (no key) header.i=@suse.de; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v30-20020a63b95e000000b0041d8ca10b57si3304430pgo.223.2022.08.12.07.23.46; Fri, 12 Aug 2022 07:24:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-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=@suse.de header.s=susede2_rsa header.b="UyM/sksT"; dkim=neutral (no key) header.i=@suse.de; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238115AbiHLOMt (ORCPT + 99 others); Fri, 12 Aug 2022 10:12:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33512 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239031AbiHLOMs (ORCPT ); Fri, 12 Aug 2022 10:12:48 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D60117A9C; Fri, 12 Aug 2022 07:12:46 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 4DFA41F93E; Fri, 12 Aug 2022 14:12:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1660313565; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=orx0gU5XjtXTeLL+wu1bGYrutnbNzbrK9E3FTi+mTho=; b=UyM/sksTfmPE5UWVg+TpkcdQ7CTap6D8o1oZsiDyGZUpWzYbic4CeYYWQFSAxY7NuuDMSI EIGJmrW8XWEJT9jbkiDZKPH5cWE/FOSR1SbAyscxl92qLN0YrEMkwrgZFZ61ijDKxTYv4B b+ZgOVAW8/mOIKsHOeNLNrmAbvMiCIM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1660313565; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=orx0gU5XjtXTeLL+wu1bGYrutnbNzbrK9E3FTi+mTho=; b=NVAjWmqAZ3y53uOlhC8yHbWTlHmlzrMQwbokOVv9UTcMqyuKoL48Zg2725hrtEXwdHhKLN 7q9ibfEUN3yYP2BQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id CA9FA13AAE; Fri, 12 Aug 2022 14:12:44 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id ebeoLtxf9mL3QQAAMHmgww (envelope-from ); Fri, 12 Aug 2022 14:12:44 +0000 Received: from localhost (brahms.olymp [local]) by brahms.olymp (OpenSMTPD) with ESMTPA id dde857b1; Fri, 12 Aug 2022 14:13:30 +0000 (UTC) From: =?UTF-8?q?Lu=C3=ADs=20Henriques?= To: Theodore Ts'o , Andreas Dilger Cc: wenqingliu0120@gmail.com, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, =?UTF-8?q?Lu=C3=ADs=20Henriques?= , Baokun Li Subject: [PATCH v3] ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0 Date: Fri, 12 Aug 2022 15:13:29 +0100 Message-Id: <20220812141329.9501-1-lhenriques@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham 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-ext4@vger.kernel.org When walking through an inode extents, the ext4_ext_binsearch_idx() function assumes that the extent header has been previously validated. However, there are no checks that verify that the number of entries (eh->eh_entries) is non-zero when depth is > 0. And this will lead to problems because the EXT_FIRST_INDEX() and EXT_LAST_INDEX() will return garbage and result in this: [ 135.245946] ------------[ cut here ]------------ [ 135.247579] kernel BUG at fs/ext4/extents.c:2258! [ 135.249045] invalid opcode: 0000 [#1] PREEMPT SMP [ 135.250320] CPU: 2 PID: 238 Comm: tmp118 Not tainted 5.19.0-rc8+ #4 [ 135.252067] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 135.255065] RIP: 0010:ext4_ext_map_blocks+0xc20/0xcb0 [ 135.256475] Code: [ 135.261433] RSP: 0018:ffffc900005939f8 EFLAGS: 00010246 [ 135.262847] RAX: 0000000000000024 RBX: ffffc90000593b70 RCX: 0000000000000023 [ 135.264765] RDX: ffff8880038e5f10 RSI: 0000000000000003 RDI: ffff8880046e922c [ 135.266670] RBP: ffff8880046e9348 R08: 0000000000000001 R09: ffff888002ca580c [ 135.268576] R10: 0000000000002602 R11: 0000000000000000 R12: 0000000000000024 [ 135.270477] R13: 0000000000000000 R14: 0000000000000024 R15: 0000000000000000 [ 135.272394] FS: 00007fdabdc56740(0000) GS:ffff88807dd00000(0000) knlGS:0000000000000000 [ 135.274510] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 135.276075] CR2: 00007ffc26bd4f00 CR3: 0000000006261004 CR4: 0000000000170ea0 [ 135.277952] Call Trace: [ 135.278635] [ 135.279247] ? preempt_count_add+0x6d/0xa0 [ 135.280358] ? percpu_counter_add_batch+0x55/0xb0 [ 135.281612] ? _raw_read_unlock+0x18/0x30 [ 135.282704] ext4_map_blocks+0x294/0x5a0 [ 135.283745] ? xa_load+0x6f/0xa0 [ 135.284562] ext4_mpage_readpages+0x3d6/0x770 [ 135.285646] read_pages+0x67/0x1d0 [ 135.286492] ? folio_add_lru+0x51/0x80 [ 135.287441] page_cache_ra_unbounded+0x124/0x170 [ 135.288510] filemap_get_pages+0x23d/0x5a0 [ 135.289457] ? path_openat+0xa72/0xdd0 [ 135.290332] filemap_read+0xbf/0x300 [ 135.291158] ? _raw_spin_lock_irqsave+0x17/0x40 [ 135.292192] new_sync_read+0x103/0x170 [ 135.293014] vfs_read+0x15d/0x180 [ 135.293745] ksys_read+0xa1/0xe0 [ 135.294461] do_syscall_64+0x3c/0x80 [ 135.295284] entry_SYSCALL_64_after_hwframe+0x46/0xb0 This patch simply adds an extra check in __ext4_ext_check(), verifying that eh_entries is not 0 when eh_depth is > 0. Link: https://bugzilla.kernel.org/show_bug.cgi?id=215941 Link: https://bugzilla.kernel.org/show_bug.cgi?id=216283 Cc: Baokun Li Signed-off-by: Luís Henriques --- fs/ext4/extents.c | 4 ++++ 1 file changed, 4 insertions(+) Changes since v2: - Dropped usage of le16_to_cpu() because we're comparing values against 0 - Use 'depth' instead of 'eh->eh_depth' because we've checked earlier that both have the same value. diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index c148bb97b527..2654fe46a1ea 100644 --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -460,6 +460,10 @@ static int __ext4_ext_check(const char *function, unsigned int line, error_msg = "invalid eh_entries"; goto corrupted; } + if (unlikely((eh->eh_entries == 0) && (eh_depth > 0))) { + error_msg = "eh_entries is 0 but eh_depth is > 0"; + goto corrupted; + } if (!ext4_valid_extent_entries(inode, eh, lblk, &pblk, depth)) { error_msg = "invalid extent entries"; goto corrupted;