cve/published/2023/CVE-2023-53077.mbox

From bippy-1.1.0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2023-53077: drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes

[WHY]
When PTEBufferSizeInRequests is zero, UBSAN reports the following
warning because dml_log2 returns an unexpected negative value:

  shift exponent 4294966273 is too large for 32-bit type 'int'

[HOW]

In the case PTEBufferSizeInRequests is zero, skip the dml_log2() and
assign the result directly.

The Linux kernel CVE team has assigned CVE-2023-53077 to this issue.


Affected and fixed versions
===========================

	Fixed in 5.10.176 with commit 7257070be70e19a9138f39009c1a26c83a8a7cfa
	Fixed in 5.15.104 with commit bec1bea2fa974e63f6059c33edde669c7894d0bc
	Fixed in 6.1.21 with commit a16394b5d661afec9a264fecac3abd87aea439ea
	Fixed in 6.2.8 with commit e12b95680821b9880cd9992c0f3555389363604f
	Fixed in 6.3 with commit 031f196d1b1b6d5dfcb0533b431e3ab1750e6189

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53077
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/gpu/drm/amd/display/dc/dml/dcn30/display_mode_vba_30.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/7257070be70e19a9138f39009c1a26c83a8a7cfa
	https://git.kernel.org/stable/c/bec1bea2fa974e63f6059c33edde669c7894d0bc
	https://git.kernel.org/stable/c/a16394b5d661afec9a264fecac3abd87aea439ea
	https://git.kernel.org/stable/c/e12b95680821b9880cd9992c0f3555389363604f
	https://git.kernel.org/stable/c/031f196d1b1b6d5dfcb0533b431e3ab1750e6189