cve/2024/CVE-2024-50269.md

### [CVE-2024-50269](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50269)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=4.14%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=583a4219841d00e96b5de55be160aa7eb7721a4d%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6ed05c68cbcae42cd52b8e53b66952bfa9c002ce%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=a2259ebaa933331c53904caf792b619ec42f0da5%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=b4ecc15d6f5a13c0bbe2777438e87e321f83faaa%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:usb: musb: sunxi: Fix accessing an released usb phyCommit 6ed05c68cbca ("usb: musb: sunxi: Explicitly release USB PHY onexit") will cause that usb phy @glue->xceiv is accessed after released.1) register platform driver @sunxi_musb_driver// get the usb phy @glue->xceivsunxi_musb_probe() -> devm_usb_get_phy().2) register and unregister platform driver @musb_drivermusb_probe() -> sunxi_musb_init()use the phy here//the phy is released heremusb_remove() -> sunxi_musb_exit() -> devm_usb_put_phy()3) register @musb_driver againmusb_probe() -> sunxi_musb_init()use the phy here but the phy has been released at 2)....Fixed by reverting the commit, namely, removing devm_usb_put_phy()from sunxi_musb_exit().

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/w4zu/Debian_security