{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98601 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98601 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-98601 and fix it if it is affected.\n\nWhat it is: CVE-2026-98601 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-98601 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-98601/ (Markdown: https://insights.sbomify.com/CVE-2026-98601/index.md)","id":"CVE-2026-98601","markdown":"https://insights.sbomify.com/CVE-2026-98601/index.md","name":"CVE-2026-98601","record":{"aliases":["BELL-CVE-2026-98601","DEBIAN-CVE-2026-98601","GHSA-f3q9-4q8h-j7xp","UBUNTU-CVE-2026-98601"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A malicious Bluetooth PCIe device can trigger out-of-bounds memory access or infinite loops in the Linux kernel driver, potentially leading to code execution or system crash.","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\nBluetooth: btintel_pcie: validate device-supplied DMA indices\n\nIn btintel_pcie_msix_rx_handle(), the driver processes RX completion\ndescriptors (urbd1) written by the PCIe device into DMA-coherent memory.\nurbd1-\u003efrbd_tag (a 16-bit field fully controlled by the device firmware\nvia DMA) is used directly as an array index into rxq-\u003ebufs[] without any\nbounds check. rxq-\u003ebufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)\nentries, while frbd_tag can be any value 0-65535. A malicious or\nmalfunctioning device can write an out-of-range frbd_tag, causing the\ndriver to dereference an out-of-bounds data_buf pointer.\n\nAdditionally, cr_hia is read from a DMA-shared index array also writable\nby the device; if the device sets cr_hia \u003e= rxq-\u003ecount, the while-loop\nnever terminates because cr_tia is wrapped via modulo rxq-\u003ecount and can\nnever equal an out-of-range cr_hia.\n\nAdd bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia\nin the TX path. Log invalid values with bt_dev_err before returning.","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: validate device-supplied DMA indices","id":"CVE-2026-98601","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":"Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough","id":"CVE-2026-98602"},"packages":[],"prev":{"headline":"Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()","id":"CVE-2026-98600"},"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-19","vendors":["Linux"]},"summary":"A malicious Bluetooth PCIe device can trigger out-of-bounds memory access or infinite loops in the Linux kernel driver, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-98601/"}