phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend There is a small window where the runtime suspend callback may run after pm_runtime_enable() and before pm_runtime_forbid(). In this case, a crash occurs because runtime suspend/resume dereferences qmp->phy pointer, which is not yet initialized: `if (!qmp->phy->init_count) {` This can also happen if user re-enables runtime-pm via the sysfs attribute before qmp phy is initialized. Similarly to other qcom phy drivers, introduce a qmp->phy_initialized variable that can be used to avoid relying on the possibly uninitialized phy pointer.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 9b28287c5dea7650e6dd317591b9e82b6e145365; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in f4e39ab1b2009a89c60e4cb9dbefb8140d405eff; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 5547fd950d6bf72de861b6934341e7bb0888640c; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 03455404fb6cbfd65842695df26739853fc1516b; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 142c5593379273264474f31d5956b1a0065cd576
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6