{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93791 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93791 is a memory corruption vulnerability in Linux, published on 24 Sep 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-93791 and fix it if it is affected.\n\nWhat it is: CVE-2026-93791 is a memory corruption vulnerability in Linux, published on 24 Sep 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-93791 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-93791/ (Markdown: https://insights.sbomify.com/CVE-2026-93791/index.md)","id":"CVE-2026-93791","markdown":"https://insights.sbomify.com/CVE-2026-93791/index.md","name":"CVE-2026-93791","record":{"aliases":["AZL-103577","BELL-CVE-2026-93791","DEBIAN-CVE-2026-93791","GHSA-6m6g-gjgc-588p","UBUNTU-CVE-2026-93791"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker with proximity can trigger memory corruption in the Linux kernel iwlwifi driver by sending crafted firmware notifications, potentially causing a crash or 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: iwlwifi: mvm: add a check on the tid coming from the firmware\n\nba_notif-\u003etid is a firmware-controlled u8 that is used directly\nas an array index into tid_data[] without any validation. Add a\nbounds check against IWL_MAX_TID_COUNT before dereferencing the\narray.","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: iwlwifi: mvm: add a check on the tid coming from the firmware","id":"CVE-2026-93791","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":"wifi: iwlwifi: mvm: fix a possible underflow","id":"CVE-2026-93792"},"packages":[],"prev":{"headline":"wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif","id":"CVE-2026-93790"},"products":["Linux"],"published":"2026-09-24","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-03","vendors":["Linux"]},"summary":"An attacker with proximity can trigger memory corruption in the Linux kernel iwlwifi driver by sending crafted firmware notifications, potentially causing a crash or code execution.","url":"https://insights.sbomify.com/CVE-2026-93791/"}