GHSA-GQGX-J6QF-XQF5
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
phy: qcom: qmp-usb: 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": [],
"aliases": [
"CVE-2026-90280"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:24Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nphy: qcom: qmp-usb: 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-\u003ephy pointer, which is not yet initialized:\n `if (!qmp-\u003ephy-\u003einit_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-\u003ephy_initialized\nvariable that can be used to avoid relying on the possibly uninitialized\nphy pointer.",
"id": "GHSA-gqgx-j6qf-xqf5",
"modified": "2026-09-17T18:31:58Z",
"published": "2026-09-17T18:31:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90280"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/03455404fb6cbfd65842695df26739853fc1516b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/142c5593379273264474f31d5956b1a0065cd576"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5547fd950d6bf72de861b6934341e7bb0888640c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b28287c5dea7650e6dd317591b9e82b6e145365"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f4e39ab1b2009a89c60e4cb9dbefb8140d405eff"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.