{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98350 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98350 is a 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-98350 and fix it if it is affected.\n\nWhat it is: CVE-2026-98350 is a 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-98350 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-98350/ (Markdown: https://insights.sbomify.com/CVE-2026-98350/index.md)","id":"CVE-2026-98350","markdown":"https://insights.sbomify.com/CVE-2026-98350/index.md","name":"CVE-2026-98350","record":{"aliases":["BELL-CVE-2026-98350","DEBIAN-CVE-2026-98350","GHSA-c6xm-v6x8-64wh","UBUNTU-CVE-2026-98350"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Wi-Fi driver","requires_auth":"none","summary":"An attacker within Wi-Fi range can read uninitialized kernel stack memory leaked to firmware due to improper initialization in the brcmfmac driver.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: brcmfmac: cyw: pass PMKID to firmware if present\n\nZero out auth_status on initialization. Otherwise, garbage will\nleak from the stack to the firmware (when ssid is less than 32 bytes\nand/or when params-\u003epmkid is set). Then, pass the params-\u003epmkid to the\nfirmware (without it, the firmware caches a garbage PMKID on successful\nauthentication and denies a subsequent association request that includes\nthe PMKID).","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: brcmfmac: cyw: pass PMKID to firmware if present","id":"CVE-2026-98350","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wifi: virt_wifi: free skb when disconnected","id":"CVE-2026-98351"},"packages":[],"prev":{"headline":"wifi: libipw: reject too-short beacon and probe responses","id":"CVE-2026-98349"},"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":"An attacker within Wi-Fi range can read uninitialized kernel stack memory leaked to firmware due to improper initialization in the brcmfmac driver.","url":"https://insights.sbomify.com/CVE-2026-98350/"}