# CVE-2026-90354: wifi: mt76: mt7915: fix double hif2 init on the non-WED path

> A double initialization bug in the mt7915 Wi-Fi driver leaks device references, potentially causing resource exhaustion and denial of service on non-WED hardware.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102173, BELL-CVE-2026-90354, DEBIAN-CVE-2026-90354, GHSA-hm9g-hpm6-69p6, UBUNTU-CVE-2026-90354

## What is CVE-2026-90354?

CVE-2026-90354 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-90354?


## How do I fix CVE-2026-90354?

Apply the vendor's patch.

## Is CVE-2026-90354 being exploited?

There is no known exploitation of CVE-2026-90354 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90354 and fix it if it is affected.

What it is: CVE-2026-90354 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90354 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90354/ (Markdown: https://insights.sbomify.com/CVE-2026-90354/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90354
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90354
- OSV: https://osv.dev/vulnerability/CVE-2026-90354

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90354/
Summaries are generated and may contain mistakes; the official description above is the record.