From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26971: clk: qcom: gcc-ipq5018: fix terminating of frequency table arrays
Date: Wed, 1 May 2024 07:22:01 +0200 [thread overview]
Message-ID: <2024050132-CVE-2024-26971-6e28@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: qcom: gcc-ipq5018: 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().
The Linux kernel CVE team has assigned CVE-2024-26971 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit e3fdbef1bab8 and fixed in 6.6.24 with commit b0cf3d200e8a
Issue introduced in 6.6 with commit e3fdbef1bab8 and fixed in 6.7.12 with commit c8f4bef06679
Issue introduced in 6.6 with commit e3fdbef1bab8 and fixed in 6.8.3 with commit 50c3acd46055
Issue introduced in 6.6 with commit e3fdbef1bab8 and fixed in 6.9-rc1 with commit 90ad946fff70
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-26971
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-ipq5018.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/b0cf3d200e8a72b6d28e6e088c062b4a98cb5eaf
https://git.kernel.org/stable/c/c8f4bef0667947b826848db1c45a645f751357c1
https://git.kernel.org/stable/c/50c3acd460551cdf9d8ac6fe0c04f2de0e8e0872
https://git.kernel.org/stable/c/90ad946fff70f312b8d23226afc38c13ddd88c4b
reply other threads:[~2024-05-01 5:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024050132-CVE-2024-26971-6e28@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).