{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98703 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98703 is a memory corruption 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-98703 and fix it if it is affected.\n\nWhat it is: CVE-2026-98703 is a memory corruption 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-98703 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-98703/ (Markdown: https://insights.sbomify.com/CVE-2026-98703/index.md)","id":"CVE-2026-98703","markdown":"https://insights.sbomify.com/CVE-2026-98703/index.md","name":"CVE-2026-98703","record":{"aliases":["AZL-109382","BELL-CVE-2026-98703","DEBIAN-CVE-2026-98703","GHSA-h4f8-3q7w-49pw","UBUNTU-CVE-2026-98703"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with root access can corrupt kernel memory via an out-of-bounds write in the minstrel_ht debugfs interface, potentially leading to code execution.","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: minstrel_ht: validate fixed rate index\n\nThe fixed_rate_idx debugfs file is a plain u32 attribute, so any value\ncan be written to it.  minstrel_ht_update_stats() then copies the value\ninto mi-\u003emax_tp_rate[] and mi-\u003emax_prob_rate, and\nminstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index\nminstrel_mcs_groups[] (42 entries) and mi-\u003egroups[].rates[] (10 entries)\nwith it.\n\nWriting e.g. 65535 selects group 4095 and rate index 15, far outside\nboth arrays.  The out-of-bounds entries are dereferenced and updated as\nstruct minstrel_rate_stats (retry counts, etc.), so the invalid index\ncorrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is\nreported as an array-index-out-of-bounds in minstrel_ht_set_rate().\n\nOnly a valid group/rate pair, or U32_MAX to disable fixed rate\nprocessing, can be used safely, so reject any other value when the\ndebugfs file is written.\n\nThe file is only reachable through a root-only debugfs mount, so this is\nnot a privilege boundary.  The out-of-bounds access is still a bug that\nmust not be reachable through a writable debugfs attribute.","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: minstrel_ht: validate fixed rate index","id":"CVE-2026-98703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"wifi: mac80211: keep fallback association elements alive","id":"CVE-2026-98704"},"packages":[],"prev":{"headline":"wifi: mac80211: reject invalid 320 MHz CSA bandwidth","id":"CVE-2026-98702"},"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 local attacker with root access can corrupt kernel memory via an out-of-bounds write in the minstrel_ht debugfs interface, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-98703/"}