GHSA-44R6-7479-RJM3
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98957"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7915: disable rx napi when removing device\n\nUnloading the mt7915e module with a MT7916 triggers multiples WARN in\n__netif_napi_del_locked() and in page_pool_disable_direct_recycling()\nbecause the driver does not disable the napi before destroying it.\n\nThis is troublesome since on MT7916 it is required to unload the module\nand reinsert it with a different enable_6ghz parameter to change the\nfrequency. The system generally becomes unstable after reinserting the\nmodule.\n\nFix it by disabling rx napi inside mt7915e itself, even through napi rx is\nenabled in the mt76 generic code. Disabling it in the mt76 generic code\nwas previously attempted and reverted because napi was disabled too\nlate and rx handlers could access freed structures. Note that the tx\nside is enabled and disabled by the mt76 generic code.\n\nIt is disabled in mt7915_stop_hardware() since, unlike\nmt7915_unregister_device(), is it also called in the probe path if an\nerror happens after rx napi is enabled.",
"id": "GHSA-44r6-7479-rjm3",
"modified": "2026-10-23T15:31:32Z",
"published": "2026-10-23T15:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98957"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0281dac1e213329b053fb02e612de7f1477a52d7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0f9afe238eeb79829f0f92f376ba3a20781caccd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7199ee4b47de0b61fa6455a1587c5ab645ebe262"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/916c484d29d82f45c281da2786fcd6a1284430ce"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.