From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26711: iio: adc: ad4130: zero-initialize clock init data
Date: Wed, 3 Apr 2024 16:56:02 +0200 [thread overview]
Message-ID: <2024040342-CVE-2024-26711-de47@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: adc: ad4130: zero-initialize clock init data
The clk_init_data struct does not have all its members
initialized, causing issues when trying to expose the internal
clock on the CLK pin.
Fix this by zero-initializing the clk_init_data struct.
The Linux kernel CVE team has assigned CVE-2024-26711 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 62094060cf3a and fixed in 6.6.18 with commit 0e0dab377509
Issue introduced in 6.2 with commit 62094060cf3a and fixed in 6.7.6 with commit 02876e2df02f
Issue introduced in 6.2 with commit 62094060cf3a and fixed in 6.8 with commit a22b0a2be69a
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-26711
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/iio/adc/ad4130.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/0e0dab37750926d4fb0144edb1c1ea0612fea273
https://git.kernel.org/stable/c/02876e2df02f8b17a593d77a0a7879a8109b27e1
https://git.kernel.org/stable/c/a22b0a2be69a36511cb5b37d948b651ddf7debf3
reply other threads:[~2024-04-03 14:58 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=2024040342-CVE-2024-26711-de47@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.