{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98957 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98957 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98957 and fix it if it is affected.\n\nWhat it is: CVE-2026-98957 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98957 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98957/ (Markdown: https://insights.sbomify.com/CVE-2026-98957/index.md)","id":"CVE-2026-98957","markdown":"https://insights.sbomify.com/CVE-2026-98957/index.md","name":"CVE-2026-98957","record":{"aliases":["AZL-110771","BELL-CVE-2026-98957","DEBIAN-CVE-2026-98957","GHSA-44r6-7479-rjm3","UBUNTU-CVE-2026-98957"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wifi: mt76: mt7915: disable rx napi when removing device","id":"CVE-2026-98957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"wifi: mt76: account non-AQL frames per peer rather than per link","id":"CVE-2026-98958"},"packages":[],"prev":{"headline":"ASoC: adau1372: allow sleepy powerdown GPIOs","id":"CVE-2026-98956"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98957/"}