{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90355 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90355 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."},"fix_prompt":"Check this codebase for CVE-2026-90355 and fix it if it is affected.\n\nWhat it is: CVE-2026-90355 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.\nExploitation: There is no known exploitation of CVE-2026-90355 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-90355/ (Markdown: https://insights.sbomify.com/CVE-2026-90355/index.md)","id":"CVE-2026-90355","markdown":"https://insights.sbomify.com/CVE-2026-90355/index.md","name":"CVE-2026-90355","record":{"aliases":["BELL-CVE-2026-90355","DEBIAN-CVE-2026-90355","GHSA-5jf9-g6v9-f6vh","UBUNTU-CVE-2026-90355"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the mt7996 Wi-Fi driver causes device inoperability and resource exhaustion after a full chip reset, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","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: mt7996: clear stale link state on full reset\n\nAfter a full chip reset, mac80211 reconfig replays interface, link and\nchannel context setup. mt7996_vif_link_add() short-circuits when the\nlink_id is still marked in mvif-\u003evalid_links, a state introduced for\npostponing link teardown to interface removal. The reset path frees the\nlink structures without clearing those bits, so the replayed setup never\nre-creates dev_info/bss_info/STA records in the restarted firmware and\nnever re-registers the link wcid, leaving the device inoperative.\n\nThe reset path also leaks every allocated MLD index: per-link indices\nand the per-vif group/remap indices are re-allocated from scratch during\nreconfig, but the old bits stay set in the masks, so repeated full\nresets exhaust the index space.\n\nClear valid_links in the reset vif iterator and reset the MLD index\nmasks alongside the existing omac_mask clearing.","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: mt7996: clear stale link state on full reset","id":"CVE-2026-90355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wifi: mt76: mt7996: free vif links after clearing wcid entries on full reset","id":"CVE-2026-90356"},"packages":[],"prev":{"headline":"wifi: mt76: mt7915: fix double hif2 init on the non-WED path","id":"CVE-2026-90354"},"products":["Linux"],"published":"2026-09-17","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-19","vendors":["Linux"]},"summary":"A flaw in the mt7996 Wi-Fi driver causes device inoperability and resource exhaustion after a full chip reset, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-90355/"}