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 727D0C6FD1F for ; Wed, 22 Mar 2023 20:10:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232011AbjCVUKy (ORCPT ); Wed, 22 Mar 2023 16:10:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50680 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232154AbjCVUKL (ORCPT ); Wed, 22 Mar 2023 16:10:11 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 42CC96A1F2; Wed, 22 Mar 2023 13:03:33 -0700 (PDT) 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 C4494622B8; Wed, 22 Mar 2023 20:02:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 712A8C4339E; Wed, 22 Mar 2023 20:02:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679515352; bh=L0ppsVkM3L1IhzDIY/wbSoHkSWthJizIcAiKa9RNvfk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=nH0cBNi7YCouv7ksIzIAmZkiLAoUsQAyBWKnzqEbcAcWzpEplotiW2ZJTmcE+Dq52 wzMAR29MtA4DrmoedbmAYOYoLJhUJQmnzMR12jlFo56HRWv6kP2XBaYhNDe4dLNo68 KIw62krylHt/+TwSzlRRfEdekLrfvxX3ltOm8wJY5G0fMP5IeR4rK2NhHElE1LPWBa wiCFN0lDDI9uiAf34IdOQCs2bIQGt9miaj/e6F7DFKTegZgwo1YWlw95Xi2dF2aQ+X zJdGWvrvp9bag2HAzjtykeYr1T7cc8aLoW1kqQE5bGsOgdd1Mott59490n3KYfWCm1 COLmwv0NjK2ng== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Wei Chen , Helge Deller , Sasha Levin , adaplas@gmail.com, linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: [PATCH AUTOSEL 5.10 07/12] fbdev: nvidia: Fix potential divide by zero Date: Wed, 22 Mar 2023 16:02:01 -0400 Message-Id: <20230322200207.1997367-7-sashal@kernel.org> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20230322200207.1997367-1-sashal@kernel.org> References: <20230322200207.1997367-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-fbdev@vger.kernel.org From: Wei Chen [ Upstream commit 92e2a00f2987483e1f9253625828622edd442e61 ] variable var->pixclock can be set by user. In case it equals to zero, divide by zero would occur in nvidiafb_set_par. Similar crashes have happened in other fbdev drivers. There is no check and modification on var->pixclock along the call chain to nvidia_check_var and nvidiafb_set_par. We believe it could also be triggered in driver nvidia from user site. Signed-off-by: Wei Chen Signed-off-by: Helge Deller Signed-off-by: Sasha Levin --- drivers/video/fbdev/nvidia/nvidia.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/video/fbdev/nvidia/nvidia.c b/drivers/video/fbdev/nvidia/nvidia.c index a372a183c1f01..f9c388a8c10e3 100644 --- a/drivers/video/fbdev/nvidia/nvidia.c +++ b/drivers/video/fbdev/nvidia/nvidia.c @@ -763,6 +763,8 @@ static int nvidiafb_check_var(struct fb_var_screeninfo *var, int pitch, err = 0; NVTRACE_ENTER(); + if (!var->pixclock) + return -EINVAL; var->transp.offset = 0; var->transp.length = 0; -- 2.39.2