[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022602-CVE-2024-52557-506d@gregkh>
Date: Wed, 26 Feb 2025 18:17:02 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-52557: drm: zynqmp_dp: Fix integer overflow in zynqmp_dp_rate_get()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm: zynqmp_dp: Fix integer overflow in zynqmp_dp_rate_get()
This patch fixes a potential integer overflow in the zynqmp_dp_rate_get()
The issue comes up when the expression
drm_dp_bw_code_to_link_rate(dp->test.bw_code) * 10000 is evaluated using 32-bit
Now the constant is a compatible 64-bit type.
Resolves coverity issues: CID 1636340 and CID 1635811
The Linux kernel CVE team has assigned CVE-2024-52557 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 28edaacb821c69241f6c0be6bbd29f7145f1b44f and fixed in 6.13.4 with commit 325d889c5403ba20a24097f64c32d27ab993c2c3
Issue introduced in 6.13 with commit 28edaacb821c69241f6c0be6bbd29f7145f1b44f and fixed in 6.14-rc1 with commit 67a615c5cb6dc33ed35492dc0d67e496cbe8de68
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-2024-52557
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/xlnx/zynqmp_dp.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/325d889c5403ba20a24097f64c32d27ab993c2c3
https://git.kernel.org/stable/c/67a615c5cb6dc33ed35492dc0d67e496cbe8de68
Powered by blists - more mailing lists