phy: qcom: snps-femto-v2: Fix possible NULL-deref on early runtime suspend
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0d75f508a9d56133a2834215959cde4605c804d1 · < 61749681e4a3629ec20b04ba2443b91016af3d2f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
phy: qcom: snps-femto-v2: Fix possible NULL-deref on early runtime suspend
Runtime PM must be enabled before creating the PHY, since phy_create() only enables runtime PM on the PHY device if it is already enabled on this parent device. However, the runtime PM callbacks dereference the hsphy instance, which is not yet ready, leaving a window where a suspend callback may trigger a NULL pointer dereference.
Take a runtime PM usage reference with pm_runtime_get_noresume() before enabling runtime PM and release it once the PHY has been created, so that no runtime suspend can run before the PHY is ready. This also prevents a short window where an unnecessary runtime suspend can occur.
Use the devres-managed version to ensure PM runtime is symmetrically disabled during driver removal for proper cleanup.
From the CVE record · Linux
The Linux kernel’s qcom snps-femto-v2 PHY driver can dereference a NULL pointer if runtime suspend runs before the PHY is ready. The input does not describe an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the qcom snps-femto-v2 PHY driver should check their kernel version; affected versions are not specified.