phy: qcom: qmp-usb-legacy: 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-legacy: 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 602059c5128a78857ca92bd22791ab640185e381; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 29449ce1f5958e36df80318878016e3ecac26b40; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5; From e464a3180a43b6596bd267f9f274e1793bfb8150 · fixed in 8e3687f7e18fe84372e86875709d56c37e7525a8
- 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