CVE-2026-90282
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.
CVSS
NVD hasn't assigned a CVSS score to this CVE (common since the April 2026 policy change).
Exploitation probability (EPSS)
- Probability of exploitation in the next 30 days: 0.20%
- Percentile among all scored CVEs: 9
- Score date: 10/5/2026
EPSS (Exploit Prediction Scoring System, FIRST) estimates how likely a vulnerability is to be exploited in the wild within 30 days. It complements CVSS (impact) and CISA KEV (confirmed exploitation).
Affected technologies (1)
⚠ AI-inferred from the description — NVD hasn't analyzed this CVE yet, these aren't verified CPEs.
References
- https://git.kernel.org/stable/c/0f9789d1b63e7d9f868ac9c29564339a4c03ceb5
- https://git.kernel.org/stable/c/29449ce1f5958e36df80318878016e3ecac26b40
- https://git.kernel.org/stable/c/52ad86ea5f98d29a7a29d9ba12e24276c6e30acd
- https://git.kernel.org/stable/c/602059c5128a78857ca92bd22791ab640185e381
- https://git.kernel.org/stable/c/8e3687f7e18fe84372e86875709d56c37e7525a8
Raw JSON (NVD)
Show
{
"id": "CVE-2026-90282",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "e464a3180a43b6596bd267f9f274e1793bfb8150",
"lessThan": "602059c5128a78857ca92bd22791ab640185e381",
"versionType": "git"
},
{
"status": "affected",
"version": "e464a3180a43b6596bd267f9f274e1793bfb8150",
"lessThan": "29449ce1f5958e36df80318878016e3ecac26b40",
"versionType": "git"
},
{
"status": "affected",
"version": "e464a3180a43b6596bd267f9f274e1793bfb8150",
"lessThan": "52ad86ea5f98d29a7a29d9ba12e24276c6e30acd",
"versionType": "git"
},
{
"status": "affected",
"version": "e464a3180a43b6596bd267f9f274e1793bfb8150",
"lessThan": "0f9789d1b63e7d9f868ac9c29564339a4c03ceb5",
"versionType": "git"
},
{
"status": "affected",
"version": "e464a3180a43b6596bd267f9f274e1793bfb8150",
"lessThan": "8e3687f7e18fe84372e86875709d56c37e7525a8",
"versionType": "git"
}
],
"programFiles": [
"drivers/phy/qualcomm/phy-qcom-qmp-usb-legacy.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.6"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.6",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/phy/qualcomm/phy-qcom-qmp-usb-legacy.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-17T17:17:24.950",
"references": [
{
"url": "https://git.kernel.org/stable/c/0f9789d1b63e7d9f868ac9c29564339a4c03ceb5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/29449ce1f5958e36df80318878016e3ecac26b40",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/52ad86ea5f98d29a7a29d9ba12e24276c6e30acd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/602059c5128a78857ca92bd22791ab640185e381",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8e3687f7e18fe84372e86875709d56c37e7525a8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nphy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend\n\nThere is a small window where the runtime suspend callback may run\nafter pm_runtime_enable() and before pm_runtime_forbid(). In this\ncase, a crash occurs because runtime suspend/resume dereferences\nqmp->phy pointer, which is not yet initialized:\n `if (!qmp->phy->init_count) {`\n\nThis can also happen if user re-enables runtime-pm via the sysfs\nattribute before qmp phy is initialized.\n\nSimilarly to other qcom phy drivers, introduce a qmp->phy_initialized\nvariable that can be used to avoid relying on the possibly uninitialized\nphy pointer."
}
],
"lastModified": "2026-09-17T17:17:24.950",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}