# CVE-2026-98957: wifi: mt76: mt7915: disable rx napi when removing device


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110771, BELL-CVE-2026-98957, DEBIAN-CVE-2026-98957, GHSA-44r6-7479-rjm3, UBUNTU-CVE-2026-98957

## What is CVE-2026-98957?

CVE-2026-98957 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: mt7915: disable rx napi when removing device

Unloading the mt7915e module with a MT7916 triggers multiples WARN in
__netif_napi_del_locked() and in page_pool_disable_direct_recycling()
because the driver does not disable the napi before destroying it.

This is troublesome since on MT7916 it is required to unload the module
and reinsert it with a different enable_6ghz parameter to change the
frequency.  The system generally becomes unstable after reinserting the
module.

Fix it by disabling rx napi inside mt7915e itself, even through napi rx is
enabled in the mt76 generic code.  Disabling it in the mt76 generic code
was previously attempted and reverted because napi was disabled too
late and rx handlers could access freed structures.  Note that the tx
side is enabled and disabled by the mt76 generic code.

It is disabled in mt7915_stop_hardware() since, unlike
mt7915_unregister_device(), is it also called in the probe path if an
error happens after rx napi is enabled.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98957 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98957 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-98957/ (Markdown: https://insights.sbomify.com/CVE-2026-98957/index.md)
```

## Sources

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

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