CVE-2024-50239
- Source
- https://cve.org/CVERecord?id=CVE-2024-50239
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50239.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2024-50239
- Downstream
- Related
- Published
- 2024-11-09T10:14:49.171Z
- Modified
- 2026-05-15T04:11:16.676559970Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usb-legacy driver.
Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend.
Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50239.json", "cna_assigner": "Linux" }- References
-
- https://git.kernel.org/stable/c/29240130ab77c80bea1464317ae2a5fd29c16a0c
- https://git.kernel.org/stable/c/7e8066811a2c43fbb5f53c2c26d389e4bab9da34
- https://git.kernel.org/stable/c/b1cffd00daa9cf499b49a0da698eff5032914f6e
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50239.json
- https://nvd.nist.gov/vuln/detail/CVE-2024-50239
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git