GHSA-HM9G-HPM6-69P6
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7915: fix double hif2 init on the non-WED path
mt7915_pci_init_hif2() was called unconditionally and again inside the WED-inactive branch. The helper increments the global hif_idx, writes the PCIe RECOG_ID register and takes a get_device() reference via mt7915_pci_get_hif2(), while removal only drops one reference. On non-WED dual-hif hardware this double-incremented hif_idx, wrote RECOG_ID twice and leaked a device reference. Only the call inside the WED-inactive branch is correct; drop the unconditional one. hif2 is already initialised to NULL.
{
"affected": [],
"aliases": [
"CVE-2026-90354"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:34Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7915: fix double hif2 init on the non-WED path\n\nmt7915_pci_init_hif2() was called unconditionally and again inside the\nWED-inactive branch. The helper increments the global hif_idx, writes the\nPCIe RECOG_ID register and takes a get_device() reference via\nmt7915_pci_get_hif2(), while removal only drops one reference. On non-WED\ndual-hif hardware this double-incremented hif_idx, wrote RECOG_ID twice and\nleaked a device reference. Only the call inside the WED-inactive branch is\ncorrect; drop the unconditional one. hif2 is already initialised to NULL.",
"id": "GHSA-hm9g-hpm6-69p6",
"modified": "2026-09-17T18:32:02Z",
"published": "2026-09-17T18:32:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90354"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/249cbaa1873550689fab136b74982cbba74c4169"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/29fbc5256c2d8448f084ff179d2e5092ecd1fc54"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3ae8ad277e2819a281b0e36b55633c8515c16ce7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/927fe8c0eb8c10295bc0018c8faa4d91f8fe98c6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bd2e8f535ae35beb45a7fcc17ec9bbf8dc4db5fe"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eac18fadc791928379b179e54636494b92f8cf86"
}
],
"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.