{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80936 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80936 is a high-severity vulnerability in Linux, published on 11 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-80936 and fix it if it is affected.\n\nWhat it is: CVE-2026-80936 is a high-severity vulnerability in Linux, published on 11 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-80936 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-80936/ (Markdown: https://insights.sbomify.com/CVE-2026-80936/index.md)","id":"CVE-2026-80936","markdown":"https://insights.sbomify.com/CVE-2026-80936/index.md","name":"CVE-2026-80936","record":{"aliases":["BELL-CVE-2026-80936","DEBIAN-CVE-2026-80936","GHSA-59xf-cqg5-4cpj","UBUNTU-CVE-2026-80936"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"low_privilege","summary":"A race condition in the mt7925 WiFi driver causes a kernel warning and potential instability when the device is stopped during a delayed power-save work queue operation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7925: cancel mlo_pm_work on stop\n\nmt7925 queues mlo_pm_work with a 5 second delay during multi-link\npower-save setup and never cancels it on the stop path. If the device is\ntorn down inside that window, the work outlives the teardown and its timer\nfires afterwards, trying to queue onto the workqueue that is already gone:\n\n  workqueue: cannot queue mt7925_mlo_pm_work [mt7925_common] on wq phy0\n  WARNING: kernel/workqueue.c:2283 at __queue_work+0x59/0xa0, CPU#1: swapper/1/0\n   call_timer_fn+0x2a/0x140\n   __run_timers+0x203/0x330\n   run_timer_softirq+0x86/0xf0\n\nmt7921 already has its own stop callback, so add one for mt7925 that\ncancels the work before calling mt792x_stop(). mt7925_ops backs both the\nPCIe and USB drivers, so this covers both.","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: mt7925: cancel mlo_pm_work on stop","id":"CVE-2026-80936","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy","id":"CVE-2026-80937"},"packages":[],"prev":{"headline":"wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copy","id":"CVE-2026-80935"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the mt7925 WiFi driver causes a kernel warning and potential instability when the device is stopped during a delayed power-save work queue operation.","url":"https://insights.sbomify.com/CVE-2026-80936/"}