From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26599: pwm: Fix out-of-bounds access in of_pwm_single_xlate()
Date: Fri, 23 Feb 2024 15:47:39 +0100 [thread overview]
Message-ID: <2024022338-CVE-2024-26599-cd65@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
pwm: Fix out-of-bounds access in of_pwm_single_xlate()
With args->args_count == 2 args->args[2] is not defined. Actually the
flags are contained in args->args[1].
The Linux kernel CVE team has assigned CVE-2024-26599 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 3ab7b6ac5d82 and fixed in 6.1.75 with commit 7b85554c7c2a
Issue introduced in 5.17 with commit 3ab7b6ac5d82 and fixed in 6.6.14 with commit e5f2b4b62977
Issue introduced in 5.17 with commit 3ab7b6ac5d82 and fixed in 6.7.2 with commit bae45b7ebb31
Issue introduced in 5.17 with commit 3ab7b6ac5d82 and fixed in 6.8-rc1 with commit a297d07b9a1e
Please see https://www.kernel.org or 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-26599
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/pwm/core.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/7b85554c7c2aee91171e038e4d5442ffa130b282
https://git.kernel.org/stable/c/e5f2b4b62977fb6c2efcbc5779e0c9dce18215f7
https://git.kernel.org/stable/c/bae45b7ebb31984b63b13c3519fd724b3ce92123
https://git.kernel.org/stable/c/a297d07b9a1e4fb8cda25a4a2363a507d294b7c9
reply other threads:[~2024-02-23 14:48 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=2024022338-CVE-2024-26599-cd65@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.