# CVE-2026-90352: wifi: mt76: mt7915: release hif2 reference on probe IRQ failure

> A resource leak in the mt7915 WiFi driver can lead to denial of service if IRQ setup fails during device probing.

- **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-102047, BELL-CVE-2026-90352, DEBIAN-CVE-2026-90352, GHSA-cqhq-7whc-695x, UBUNTU-CVE-2026-90352

## What is CVE-2026-90352?

CVE-2026-90352 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: release hif2 reference on probe IRQ failure

The hif2 reference obtained by mt7915_pci_init_hif2() is only released on
error paths that key off dev->hif2, which is not assigned until after the
IRQ setup. If pci_alloc_irq_vectors() or the primary devm_request_irq()
fails, the reference leaks. Drop it explicitly on those paths via
mt7915_put_hif2().

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


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

Apply the vendor's patch.

## Is CVE-2026-90352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90352 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-90352 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-90352/ (Markdown: https://insights.sbomify.com/CVE-2026-90352/index.md)
```

## Sources

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

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