CVE-2024-50269: usb: musb: sunxi: Fix accessing an released usb phy
In the Linux kernel, the following vulnerability has been resolved:
usb: musb: sunxi: Fix accessing an released usb phy
Commit 6ed05c68cbca ("usb: musb: sunxi: Explicitly release USB PHY on exit") will cause that usb phy @glue->xceiv is accessed after released.
1) register platform driver @sunximusbdriver // get the usb phy @glue->xceiv sunximusbprobe() -> devmusbgetphy().
2) register and unregister platform driver @musbdriver musbprobe() -> sunximusbinit() use the phy here //the phy is released here musbremove() -> sunximusbexit() -> devmusbputphy()
3) register @musbdriver again musbprobe() -> sunximusbinit() use the phy here but the phy has been released at 2). ...
Fixed by reverting the commit, namely, removing devmusbputphy() from sunximusbexit().
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50269?
The severity of CVE-2024-50269 is classified as moderate.
How do I fix CVE-2024-50269?
To fix CVE-2024-50269, users should update their Linux kernel to a version that includes the relevant patches.
Which Linux kernel versions are affected by CVE-2024-50269?
CVE-2024-50269 affects multiple Linux kernel versions ranging from 4.4.95 to 6.12-rc6.
Is CVE-2024-50269 exploitation possible?
Exploitation of CVE-2024-50269 may lead to potential security risks due to improper access post-release of USB PHY.
What is the exploit implications of CVE-2024-50269?
The implications of exploiting CVE-2024-50269 can include system instability and unauthorized access to USB device functionalities.