[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061856-CVE-2022-50079-b3a5@gregkh>
Date: Wed, 18 Jun 2025 13:02:24 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50079: drm/amd/display: Check correct bounds for stream encoder instances for DCN303
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check correct bounds for stream encoder instances for DCN303
[Why & How]
eng_id for DCN303 cannot be more than 1, since we have only two
instances of stream encoders.
Check the correct boundary condition for engine ID for DCN303 prevent
the potential out of bounds access.
The Linux kernel CVE team has assigned CVE-2022-50079 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit cd6d421e3d1ad5926b74091254e345db730e7706 and fixed in 5.15.63 with commit 82a27c1855445d48aacc67b0c0640f3dadebe52f
Issue introduced in 5.14 with commit cd6d421e3d1ad5926b74091254e345db730e7706 and fixed in 5.19.4 with commit 4c31dca1799612eb3b6413e3e574f90c3fb8f865
Issue introduced in 5.14 with commit cd6d421e3d1ad5926b74091254e345db730e7706 and fixed in 6.0 with commit 89b008222c2bf21e50219725caed31590edfd9d1
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-2022-50079
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/dcn303/dcn303_resource.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/82a27c1855445d48aacc67b0c0640f3dadebe52f
https://git.kernel.org/stable/c/4c31dca1799612eb3b6413e3e574f90c3fb8f865
https://git.kernel.org/stable/c/89b008222c2bf21e50219725caed31590edfd9d1
Powered by blists - more mailing lists