Subject: CVE-2024-26968: clk: qcom: gcc-ipq9574: fix terminating of frequency table arrays

From: Greg Kroah-Hartman <[email-masked]>

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

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

clk: qcom: gcc-ipq9574: fix terminating of frequency table arrays

The frequency table arrays are supposed to be terminated with an
empty element. Add such entry to the end of the arrays where it
is missing in order to avoid possible out-of-bound access when
the table is traversed by functions like qcom_find_freq() or
qcom_find_freq_floor().

Only compile tested.

The Linux kernel CVE team has assigned CVE-2024-26968 to this issue.

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

	Issue introduced in 6.4 with commit d75b82cff488 and fixed in 6.6.24 with commit 0204247cf366
	Issue introduced in 6.4 with commit d75b82cff488 and fixed in 6.7.12 with commit 1723629fea8a
	Issue introduced in 6.4 with commit d75b82cff488 and fixed in 6.8.3 with commit 604f2d7c4672
	Issue introduced in 6.4 with commit d75b82cff488 and fixed in 6.9 with commit bd2b6395671d

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-26968
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/clk/qcom/gcc-ipq9574.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/0204247cf3669b6021fb745c3b7f37ae392ab19c
	https://git.kernel.org/stable/c/1723629fea8a4e75333196866e10d395463dca72
	https://git.kernel.org/stable/c/604f2d7c46727c5e24fc7faddc980bc1cc0b1011
	https://git.kernel.org/stable/c/bd2b6395671d823caa38d8e4d752de2448ae61e1