CVE-2024-26963: usb: dwc3-am62: fix module unload/reload behavior
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 pmruntimegetsync() to make sure module is active before doing any register operations.
Doing a pmruntimeputsync() 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 clkcoredisable+0xb0/0xb8
We called ofplatformpopulate() in .probe() so call the cleanup function ofplatformdepopulate() in .remove(). Get rid of the now unnnecessary dwc3tiremovecore(). Without this, module re-load doesn't work properly.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-26963?
CVE-2024-26963 is classified as a high-severity vulnerability due to its potential impact on system stability and functionality.
How do I fix CVE-2024-26963?
To resolve CVE-2024-26963, update to the latest stable versions of the Linux kernel, specifically 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.
Which systems are affected by CVE-2024-26963?
CVE-2024-26963 affects systems running specific versions of the Linux kernel that have the dwc3-am62 module.
What are the risks associated with CVE-2024-26963?
The risks associated with CVE-2024-26963 include unexpected module behavior and potential system crashes during runtime suspension.
Is CVE-2024-26963 being actively exploited?
As of the latest updates, there is no public evidence indicating that CVE-2024-26963 is being actively exploited in the wild.