{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98325 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98325 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-98325 and fix it if it is affected.\n\nWhat it is: CVE-2026-98325 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-98325 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-98325/ (Markdown: https://insights.sbomify.com/CVE-2026-98325/index.md)","id":"CVE-2026-98325","markdown":"https://insights.sbomify.com/CVE-2026-98325/index.md","name":"CVE-2026-98325","record":{"aliases":["AZL-105993","BELL-CVE-2026-98325","DEBIAN-CVE-2026-98325","GHSA-3437-mcr8-jcvh","UBUNTU-CVE-2026-98325"],"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 memory handling flaw in the Linux kernel Wi-Fi subsystem can lead to resource leaks or crashes during transmission failures, requiring a kernel patch.","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: mac80211: set up the TX info early to fix failure paths\n\nThe previous commit 2c51457d930f (\"wifi: mac80211: free ack status\nframe on TX header build failure\") cleaned up the leak, but still\nleft the code a bit messy and the failed SKB didn't get reported\nto userspace.\n\nFix this up by initialising skb-\u003ecb[] earlier, which allows using\nieee80211_free_txskb() and therefore reports it for the failure\nin ieee80211_build_hdr(), and unifies the ieee80211_skb_resize()\nfailure path with it.","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: set up the TX info early to fix failure paths","id":"CVE-2026-98325","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"wifi: mac80211: mesh: release the channel if start fails","id":"CVE-2026-98326"},"packages":[],"prev":{"headline":"dmaengine: pxa: fix double counting of the hw descriptors","id":"CVE-2026-98324"},"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 handling flaw in the Linux kernel Wi-Fi subsystem can lead to resource leaks or crashes during transmission failures, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-98325/"}