{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98307 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98307 is a memory corruption vulnerability in Linux, published on 6 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-98307 and fix it if it is affected.\n\nWhat it is: CVE-2026-98307 is a memory corruption vulnerability in Linux, published on 6 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-98307 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-98307/ (Markdown: https://insights.sbomify.com/CVE-2026-98307/index.md)","id":"CVE-2026-98307","markdown":"https://insights.sbomify.com/CVE-2026-98307/index.md","name":"CVE-2026-98307","record":{"aliases":["AZL-106227","BELL-CVE-2026-98307","DEBIAN-CVE-2026-98307","GHSA-79xr-q5vm-65jg","UBUNTU-CVE-2026-98307"],"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":"none","summary":"A memory leak in the ath11k WiFi driver can lead to resource exhaustion and denial of service when firmware crashes occur.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all()\n\nWhen mac80211 removes a sta, it calls .sta_state() which in turn calls\nath11k_mac_station_remove(). In that function we clean up both peers \u0026\narsta related resources.\n\nBut when the firmware crashes, ath11k calls ieee80211_restart_hw(), which\nassumes that all driver related resources are cleaned up beforehand. This\ncleanup is supposedly done by ath11k_mac_peer_cleanup_all() but does not\nin fact free arsta-\u003erx_stats / tx_stats.\n\nExtract the arsta cleanup from ath11k_mac_station_remove() into a\nnew ath11k_mac_station_cleanup() and call it from both there and\nath11k_mac_peer_cleanup_all().\n\nThis should handle kmemleaks reports like:\n\tunreferenced object 0xffffff801ae66400 (size 1024):\n\t  comm \"hostapd\", pid 1306, jiffies 4295011565\n\t  hex dump (first 32 bytes):\n\t    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n\t    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n\t  backtrace (crc d61c08ec):\n\t    kmemleak_alloc+0x3c/0x50\n\t    __kmalloc_cache_noprof+0x2b0/0x3e0\n\t    ath11k_mac_op_sta_state+0x1dc/0xb10\n\t    drv_sta_state+0xac/0x6f8\n\t    sta_info_insert_rcu+0x314/0x5e0\n\t    sta_info_insert+0x14/0x38\n\t    ieee80211_add_station+0x10c/0x1a0\n\t    nl80211_new_station+0x3e8/0x680\n\t    genl_family_rcv_msg_doit+0xc0/0x120\n\t    genl_rcv_msg+0x1b4/0x258\n\t    netlink_rcv_skb+0x4c/0x108\n\t    genl_rcv+0x38/0x60\n\t    netlink_unicast+0x190/0x278\n\t    netlink_sendmsg+0x15c/0x370\n\t    ____sys_sendmsg+0x120/0x290\n\t    ___sys_sendmsg+0x70/0xa0\n\nTested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1","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: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all()","id":"CVE-2026-98307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ALSA: hda: trace PCM open only after assigning a stream","id":"CVE-2026-98308"},"packages":[],"prev":{"headline":"seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation","id":"CVE-2026-98306"},"products":["Linux"],"published":"2026-10-06","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 memory leak in the ath11k WiFi driver can lead to resource exhaustion and denial of service when firmware crashes occur.","url":"https://insights.sbomify.com/CVE-2026-98307/"}