From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26997: usb: dwc2: host: Fix dereference issue in DDMA completion flow.
Date: Wed, 1 May 2024 07:30:58 +0200 [thread overview]
Message-ID: <2024050145-CVE-2024-26997-b8bf@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc2: host: Fix dereference issue in DDMA completion flow.
Fixed variable dereference issue in DDMA completion flow.
The Linux kernel CVE team has assigned CVE-2024-26997 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.154 with commit 32d3f2f108eb and fixed in 5.15.157 with commit 8aa5c28ac65c
Issue introduced in 6.1.84 with commit bc48eb1b53ce and fixed in 6.1.88 with commit 9de10b59d168
Issue introduced in 6.6.24 with commit 8d310e5d702c and fixed in 6.6.29 with commit 8a139fa44870
Issue introduced in 6.8.3 with commit 8b7c57ab6f6b and fixed in 6.8.8 with commit 55656b2afd5f
Issue introduced in 6.9-rc2 with commit b258e4268850 and fixed in 6.9-rc5 with commit eed04fa96c48
Issue introduced in 4.19.312 with commit dca1dc1e99e0
Issue introduced in 5.4.274 with commit 693bbbccd9c7
Issue introduced in 5.10.215 with commit db4fa0c8e811
Issue introduced in 6.7.12 with commit c4046e703e00
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-26997
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/usb/dwc2/hcd_ddma.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/8aa5c28ac65cb5e7f1b9c0c3238c00b661dd2b8c
https://git.kernel.org/stable/c/9de10b59d16880a0a3ae2876c142fe54ce45d816
https://git.kernel.org/stable/c/8a139fa44870e84ac228b7b76423a49610e5ba9a
https://git.kernel.org/stable/c/55656b2afd5f1efcec4245f3e7e814c2a9ef53f6
https://git.kernel.org/stable/c/eed04fa96c48790c1cce73c8a248e9d460b088f8
reply other threads:[~2024-05-01 5:31 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=2024050145-CVE-2024-26997-b8bf@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).