CVE-2026-90354: wifi: mt76: mt7915: fix double hif2 init on the non-WED path
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 249cbaa1873550689fab136b74982cbba74c4169, 29fbc5256c2d8448f084ff179d2e5092ecd1fc54, 3ae8ad277e2819a281b0e36b55633c8515c16ce7.
Low priority for now. Upgrade to Linux Linux 249cbaa1873550689fab136b74982cbba74c4169, 29fbc5256c2d8448f084ff179d2e5092ecd1fc54, 3ae8ad277e2819a281b0e36b55633c8515c16ce7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In 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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before eac18fadc791928379b179e54636494b92f8cf86affected · git
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before 927fe8c0eb8c10295bc0018c8faa4d91f8fe98c6affected · git
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before bd2e8f535ae35beb45a7fcc17ec9bbf8dc4db5feaffected · git
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before 249cbaa1873550689fab136b74982cbba74c4169affected · git
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before 29fbc5256c2d8448f084ff179d2e5092ecd1fc54affected · git
- cacdd67812c6df824704ac078f1770188a485ff9 and later · before 3ae8ad277e2819a281b0e36b55633c8515c16ce7affected · git
- before 5.18not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90352Sep 17, 2026 · wifi: mt76: mt7915: release hif2 reference on probe IRQ failure0Monitor
- ← EarlierCVE-2026-90353Sep 17, 2026 · wifi: mt76: mt7915: fix ext PHY use-after-free on register error path28Monitor
- Later →CVE-2026-90355Sep 17, 2026 · wifi: mt76: mt7996: clear stale link state on full reset0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 249cbaa1873550689fab136b74982cbba74c4169 | Vendor (CNA) |
| Linux Linux | 29fbc5256c2d8448f084ff179d2e5092ecd1fc54 | Vendor (CNA) |
| Linux Linux | 3ae8ad277e2819a281b0e36b55633c8515c16ce7 | Vendor (CNA) |
| Linux Linux | 927fe8c0eb8c10295bc0018c8faa4d91f8fe98c6 | Vendor (CNA) |
| Linux Linux | bd2e8f535ae35beb45a7fcc17ec9bbf8dc4db5fe | Vendor (CNA) |
| Linux Linux | eac18fadc791928379b179e54636494b92f8cf86 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/29fbc5256c2d8448f084ff179d2e5092ecd1fc54
- git.kernel.org/stable/c/3ae8ad277e2819a281b0e36b55633c8515c16ce7
- git.kernel.org/stable/c/927fe8c0eb8c10295bc0018c8faa4d91f8fe98c6
- git.kernel.org/stable/c/bd2e8f535ae35beb45a7fcc17ec9bbf8dc4db5fe
- git.kernel.org/stable/c/eac18fadc791928379b179e54636494b92f8cf86
Vendor advisories and official records. Exploit/PoC links are deliberately left out.