Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3365862pxb; Mon, 17 Jan 2022 18:43:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJxQobdO734FZ4pl1KOEBIUleW/AHq1wrcO7KZxmNY4O35SAtt8PCCMzCztDJACJef3EGMyq X-Received: by 2002:a17:90b:378f:: with SMTP id mz15mr38166446pjb.78.1642473800337; Mon, 17 Jan 2022 18:43:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642473800; cv=none; d=google.com; s=arc-20160816; b=hvy3HovRqJvU7M/1D8yOfMNbSpLAYe29bKZ3wspjIjrga7GP/g6VDQbaGsOJa9aFpU BmPbv/XrLHDF8MQ/4EB0SGifb7E9SmIOa93kvhCWL+ziK/8xFFuV8Y2RMo1NXq0+MGK1 apV+Sk3ilQDvFvAad/Ki1EoYidHh+7m77L3XtlUDy2IiR62PNtjd265eoO0rjaaWr81f JBzKyLFqKOkAYvHioSn7tpmHCB9OVUYxCkilwARhzHrIBA0jCfjp3RsdRiLnt6VFKpAG 22TXDskQwmUctyh5Y1gww02w+uiwM5kGfqYs6v51GPE9odgFFZRYhe0SI5A6g910q8NH 1IAQ== 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 :dkim-signature; bh=lIDjzbfuu6u4+78Vb8eAOO5gxo04jkX4bQAczm3hq2E=; b=IC3g2LebjEtl73Eq36TZeWdLVrsIA4ZRCQyUzxw0iSkklyRZ2LdAH/ptbZuuH1Z0+S pKPwPPROgdx966DJQRl8t9GkBOLwAmEj+XSmecUoelwtWMYFVSSzlVkp15jcTL5vF9uT zjEoC0QVzeX8KZLnBpSyRQ6m0sIcPNPtHvBvsQyDx2Ce1KimnFHCDPycqe6Z65jDpy7h MW2oF9PnD8wjjlZejE82/NNzhH3RnYqSrtR/Q3mbgl+Tt0c0X9twKIRVbUlAd1gOneer NfdfN33qdOv99nDTG1q+GB6gc1BgQ+th8goSLgH6+psb+BYmza0nht75+qnwt3a4o3ZQ Algw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=s0cS+9bw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w16si5126705pll.613.2022.01.17.18.43.08; Mon, 17 Jan 2022 18:43:20 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=s0cS+9bw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238030AbiAQRBH (ORCPT + 99 others); Mon, 17 Jan 2022 12:01:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44916 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241615AbiAQRAV (ORCPT ); Mon, 17 Jan 2022 12:00:21 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E89A3C061774; Mon, 17 Jan 2022 09:00:20 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 885AC611C3; Mon, 17 Jan 2022 17:00:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C22CC36AE7; Mon, 17 Jan 2022 17:00:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1642438820; bh=GzbYbsXc5BwyTSbLqMt453HSpU4UrE4xgXx+YQpBbjc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=s0cS+9bwYabGC70K1zId4iwtZODx/fifuH+ko9BN+94JtYMOmY9NTb3+xWJ7wHiER miAlunUGCptbwry/rHfQzmARwqt8Kwq3UdoRVINBlh5mqzHegQLDz/Q9J1frzcsy1v jQffY2a2Ce+eEpcbQviZewFRBaq3G+CB0Wa2pDZtbZmh8NMbGJe+UJrCTv+NJ/S3Zu 7DEiYM/WGL1G6TDp1cKV39S1hy/AQ2JS0OoTJ1uIk2atIofvfGyOE3HerxCdDieNSZ U7L7PsZFNpP6Wde7kUO978Xpn/IICgmERRSBiiMcKx7DN9oDRsxLJLr01BNToGmn91 mGoVI7Bpb409Q== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Jan Kara , syzbot+9ca499bb57a2b9e4c652@syzkaller.appspotmail.com, Sasha Levin , jack@suse.com Subject: [PATCH AUTOSEL 5.16 32/52] udf: Fix error handling in udf_new_inode() Date: Mon, 17 Jan 2022 11:58:33 -0500 Message-Id: <20220117165853.1470420-32-sashal@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220117165853.1470420-1-sashal@kernel.org> References: <20220117165853.1470420-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jan Kara [ Upstream commit f05f2429eec60851b98bdde213de31dab697c01b ] When memory allocation of iinfo or block allocation fails, already allocated struct udf_inode_info gets freed with iput() and udf_evict_inode() may look at inode fields which are not properly initialized. Fix it by marking inode bad before dropping reference to it in udf_new_inode(). Reported-by: syzbot+9ca499bb57a2b9e4c652@syzkaller.appspotmail.com Signed-off-by: Jan Kara Signed-off-by: Sasha Levin --- fs/udf/ialloc.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/udf/ialloc.c b/fs/udf/ialloc.c index 2ecf0e87660e3..b5d611cee749c 100644 --- a/fs/udf/ialloc.c +++ b/fs/udf/ialloc.c @@ -77,6 +77,7 @@ struct inode *udf_new_inode(struct inode *dir, umode_t mode) GFP_KERNEL); } if (!iinfo->i_data) { + make_bad_inode(inode); iput(inode); return ERR_PTR(-ENOMEM); } @@ -86,6 +87,7 @@ struct inode *udf_new_inode(struct inode *dir, umode_t mode) dinfo->i_location.partitionReferenceNum, start, &err); if (err) { + make_bad_inode(inode); iput(inode); return ERR_PTR(err); } -- 2.34.1