{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80939 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80939 is a denial of service 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-80939 and fix it if it is affected.\n\nWhat it is: CVE-2026-80939 is a denial of service 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-80939 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-80939/ (Markdown: https://insights.sbomify.com/CVE-2026-80939/index.md)","id":"CVE-2026-80939","markdown":"https://insights.sbomify.com/CVE-2026-80939/index.md","name":"CVE-2026-80939","record":{"aliases":["BELL-CVE-2026-80939","DEBIAN-CVE-2026-80939","GHSA-q754-7p54-36jv","UBUNTU-CVE-2026-80939"],"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 missing shutdown callback in the rtw89 PCI driver causes kernel panics during warm reboot on arm64 platforms due to asynchronous SError interrupts.","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: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot\n\nSince the hardware rfkill polling was introduced, arm64 platforms can\npanic with an asynchronous SError during warm reboot:\n\n  SError Interrupt on CPU8, code 0x00000000be000011 -- SError\n  Workqueue: events_power_efficient rfkill_poll [rfkill]\n    rtw89_pci_ops_read8+0x94/0x160 [rtw89_pci]\n    rtw89_core_rfkill_poll+0x50/0x1e0 [rtw89_core]\n    rtw89_ops_rfkill_poll+0x40/0x68 [rtw89_core]\n    ieee80211_rfkill_poll+0x3c/0x70 [mac80211]\n    cfg80211_rfkill_poll+0x40/0x2a0 [cfg80211]\n    rfkill_poll+0x30/0x88 [rfkill]\n  Kernel panic - not syncing: Asynchronous SError Interrupt\n\nOn the reboot path the kernel only runs device_shutdown(), which calls\neach driver's .shutdown callback; .remove is not invoked.  The rtw89 PCI\ndriver had no .shutdown callback, so nothing stopped the rfkill polling\nwork while the platform was tearing the PCIe link down.  Once the link\nis gone, the next MMIO read from the poll handler targets a\nnon-responding device and is reported as a fatal asynchronous SError on\narm64.\n\nAdd rtw89_pci_shutdown(), wired to all rtw89 PCI device drivers, which\nsets a new RTW89_FLAG_SHUTDOWN flag (mirroring the USB\nRTW89_FLAG_UNPLUGGED pattern).  When the flag is set,\nrtw89_ops_rfkill_poll() returns early, so no MMIO read is issued to the\nchip after shutdown begins and the SError no longer occurs.\n\nThis does not call the full .remove path from .shutdown, to keep the\nshutdown handler minimal and avoid running the non-idempotent teardown\ntwice.","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: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot","id":"CVE-2026-80939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"wifi: rtw88: pci: fix resource leak on failed NAPI setup","id":"CVE-2026-80940"},"packages":[],"prev":{"headline":"wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex","id":"CVE-2026-80938"},"products":["Linux"],"published":"2026-09-11","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 missing shutdown callback in the rtw89 PCI driver causes kernel panics during warm reboot on arm64 platforms due to asynchronous SError interrupts.","url":"https://insights.sbomify.com/CVE-2026-80939/"}