{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98706 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98706 is a vulnerability in Linux, published on 18 Oct 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-98706 and fix it if it is affected.\n\nWhat it is: CVE-2026-98706 is a vulnerability in Linux, published on 18 Oct 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-98706 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-98706/ (Markdown: https://insights.sbomify.com/CVE-2026-98706/index.md)","id":"CVE-2026-98706","markdown":"https://insights.sbomify.com/CVE-2026-98706/index.md","name":"CVE-2026-98706","record":{"aliases":["AZL-108962","BELL-CVE-2026-98706","DEBIAN-CVE-2026-98706","GHSA-24rr-93xv-vqrr","UBUNTU-CVE-2026-98706"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Wi-Fi","requires_auth":"none","summary":"A race condition in Linux kernel Wi-Fi station teardown allows denial of service by triggering use-after-free or state inconsistencies during power-save frame delivery.","user_interaction":"not_required","vuln_class":"race_condition"},"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: mac80211: drain PS delivery work during station teardown\n\nRemoving an AP or mesh station can notify the driver and wake TXQs after\nthe station has already been removed from the driver, and can update\nnum_sta_ps and the power-save queues after station cleanup has purged\nthem.\n\nsta_deliver_ps_frames() tests sta-\u003edead only before it starts delivery. A\nworker that passes that test can be delayed while teardown sets sta-\u003edead\nand removes the station from the driver; when it resumes it still runs the\nfull delivery.\n\nThe existing cancel_work_sync() sits near the end of\n__cleanup_single_sta(), after the final driver state transition and after\nPS accounting and queue purging, so it drains the worker only once the\nstate it has to protect has already changed. Before commit d34ba2168a3c\n(\"mac80211: don't delay station destruction\") cleanup was deferred\nthrough the same ordered workqueue as the delivery work, which kept the\ntwo ordered.\n\nCancel the work after setting sta-\u003edead and before moving the driver\nstate, and move the existing cancellation to the start of\n__cleanup_single_sta(). The first drain closes the driver-lifetime window;\ndriver callbacks during the remaining state transitions can still queue\ndrv_deliver_wk through ieee80211_sta_block_awake(), so retain the second\ndrain at the start of __cleanup_single_sta(). That drain also covers\ninsertion failures, which reach cleanup without setting sta-\u003edead.","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: mac80211: drain PS delivery work during station teardown","id":"CVE-2026-98706","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"wifi: mac80211: shut down RX BA session timer on teardown","id":"CVE-2026-98707"},"packages":[],"prev":{"headline":"wifi: mac80211: account proxy paths against the mesh path limit","id":"CVE-2026-98705"},"products":["Linux"],"published":"2026-10-18","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-21","vendors":["Linux"]},"summary":"A race condition in Linux kernel Wi-Fi station teardown allows denial of service by triggering use-after-free or state inconsistencies during power-save frame delivery.","url":"https://insights.sbomify.com/CVE-2026-98706/"}