| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-26967: clk: qcom: camcc-sc8280xp: fix terminating of frequency table arrays |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| clk: qcom: camcc-sc8280xp: 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-26967 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.8 with commit ff93872a9c6168992ee41f2da9d9c3b8a6f8a8e5 and fixed in 6.8.3 with commit 93ff48729211dae55df5d216023be4528d29babb |
| Issue introduced in 6.8 with commit ff93872a9c6168992ee41f2da9d9c3b8a6f8a8e5 and fixed in 6.9 with commit 6a3d70f7802a98e6c28a74f997a264118b9f50cd |
| |
| 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-26967 |
| 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/camcc-sc8280xp.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/93ff48729211dae55df5d216023be4528d29babb |
| https://git.kernel.org/stable/c/6a3d70f7802a98e6c28a74f997a264118b9f50cd |
