From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26963: usb: dwc3-am62: fix module unload/reload behavior
Date: Wed, 1 May 2024 07:21:53 +0200 [thread overview]
Message-ID: <2024050130-CVE-2024-26963-3eac@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3-am62: fix module unload/reload behavior
As runtime PM is enabled, the module can be runtime
suspended when .remove() is called.
Do a pm_runtime_get_sync() to make sure module is active
before doing any register operations.
Doing a pm_runtime_put_sync() should disable the refclk
so no need to disable it again.
Fixes the below warning at module removel.
[ 39.705310] ------------[ cut here ]------------
[ 39.710004] clk:162:3 already disabled
[ 39.713941] WARNING: CPU: 0 PID: 921 at drivers/clk/clk.c:1090 clk_core_disable+0xb0/0xb8
We called of_platform_populate() in .probe() so call the
cleanup function of_platform_depopulate() in .remove().
Get rid of the now unnnecessary dwc3_ti_remove_core().
Without this, module re-load doesn't work properly.
The Linux kernel CVE team has assigned CVE-2024-26963 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit e8784c0aec03 and fixed in 6.1.84 with commit 6c6a45645a2e
Issue introduced in 5.19 with commit e8784c0aec03 and fixed in 6.6.24 with commit 7dfed9855397
Issue introduced in 5.19 with commit e8784c0aec03 and fixed in 6.7.12 with commit 629b534c42d0
Issue introduced in 5.19 with commit e8784c0aec03 and fixed in 6.8.3 with commit 3895780fabd1
Issue introduced in 5.19 with commit e8784c0aec03 and fixed in 6.9-rc1 with commit 6661befe4100
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-26963
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/dwc3/dwc3-am62.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/6c6a45645a2e6a272dfde14eddbb6706de63c25d
https://git.kernel.org/stable/c/7dfed9855397d0df4c6f748d1f66547ab3bad766
https://git.kernel.org/stable/c/629b534c42d04f0797980f2d1ed105fdb8906975
https://git.kernel.org/stable/c/3895780fabd120d0fbd54354014e85207b25687c
https://git.kernel.org/stable/c/6661befe41009c210efa2c1bcd16a5cc4cff8a06
reply other threads:[~2024-05-01 5:23 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=2024050130-CVE-2024-26963-3eac@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).