{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98291 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98291 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-98291 and fix it if it is affected.\n\nWhat it is: CVE-2026-98291 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-98291 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-98291/ (Markdown: https://insights.sbomify.com/CVE-2026-98291/index.md)","id":"CVE-2026-98291","markdown":"https://insights.sbomify.com/CVE-2026-98291/index.md","name":"CVE-2026-98291","record":{"aliases":["BELL-CVE-2026-98291","DEBIAN-CVE-2026-98291","GHSA-7r69-vgp4-2564","UBUNTU-CVE-2026-98291"],"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 Bluetooth","requires_auth":"none","summary":"An off-by-one error in the Linux kernel Bluetooth driver allows out-of-bounds memory access, potentially leading to system crashes or code execution.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\nBluetooth: btintel_pcie: fix off-by-one bounds check in RX submit\n\nbtintel_pcie_submit_rx() used frbd_index \u003e rxq-\u003ecount to guard the\nFRBD array access, allowing frbd_index == rxq-\u003ecount to pass through\nand index one element past the end of the array. Change the check to\n\u003e= rxq-\u003ecount so every out-of-range index is rejected.\n\nThis issue was reported by Claude Mythos.","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":"Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit","id":"CVE-2026-98291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access","id":"CVE-2026-98292"},"packages":[],"prev":{"headline":"Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup","id":"CVE-2026-98290"},"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 off-by-one error in the Linux kernel Bluetooth driver allows out-of-bounds memory access, potentially leading to system crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-98291/"}