CVE-2026-90281

phy: qcom: snps-femto-v2: Fix possible NULL-deref on early runtime suspend

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0d75f508a9d56133a2834215959cde4605c804d15.9
Vendor states this is fixed in 0c5c08c94dd64c05679970d4eed8b06d36a889a8 (fixed)
Vendor states this is fixed in 1027b1d4e29756dfbf74ef8743456a1efa3679f0 (fixed)
Vendor states this is fixed in 34293f5a8982a06c40af69c8c7c856b5837ac652 (fixed)
Vendor states this is fixed in 3ddf41938fee3d148a170c31e76b0515a522ef7e (fixed)
Vendor states this is fixed in 61749681e4a3629ec20b04ba2443b91016af3d2f (fixed)
Vendor states this is fixed in 82cb1aedf4bdb279cf8853fe8f39bec4e6cffa0a (fixed)
Vendor states this is fixed in b85bbec72fa813b60e093c6bb36ae232b9b0eb5e (fixed)
Vendor states this is fixed in c271a6926ea7d3c9566b033d63fd4e8c488dc860 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card