CVE-2026-90282
N/A
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | e464a3180a43b6596bd267f9f274e1793bfb8150 < 602059c5128a78857ca92bd22791ab640185e381 | affected |
| Linux | Linux | e464a3180a43b6596bd267f9f274e1793bfb8150 < 29449ce1f5958e36df80318878016e3ecac26b40 | affected |
| Linux | Linux | e464a3180a43b6596bd267f9f274e1793bfb8150 < 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd | affected |
| Linux | Linux | e464a3180a43b6596bd267f9f274e1793bfb8150 < 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5 | affected |
| Linux | Linux | e464a3180a43b6596bd267f9f274e1793bfb8150 < 8e3687f7e18fe84372e86875709d56c37e7525a8 | affected |
| Linux | Linux | 6.6 | affected |
| Linux | Linux | 0 < 6.6 | unaffected |
| Linux | Linux | 6.6.157 <= 6.6.* | unaffected |
| Linux | Linux | 6.12.110 <= 6.12.* | unaffected |
| Linux | Linux | 6.18.52 <= 6.18.* | unaffected |
| Linux | Linux | 7.2.6 <= 7.2.* | unaffected |
| Linux | Linux | 7.3-rc1 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/602059c5128a78857ca92bd22791ab640185e381
- https://git.kernel.org/stable/c/29449ce1f5958e36df80318878016e3ecac26b40
- https://git.kernel.org/stable/c/52ad86ea5f98d29a7a29d9ba12e24276c6e30acd
- https://git.kernel.org/stable/c/0f9789d1b63e7d9f868ac9c29564339a4c03ceb5
- https://git.kernel.org/stable/c/8e3687f7e18fe84372e86875709d56c37e7525a8
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.