{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98735 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98735 is an use after free 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-98735 and fix it if it is affected.\n\nWhat it is: CVE-2026-98735 is an use after free 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-98735 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-98735/ (Markdown: https://insights.sbomify.com/CVE-2026-98735/index.md)","id":"CVE-2026-98735","markdown":"https://insights.sbomify.com/CVE-2026-98735/index.md","name":"CVE-2026-98735","record":{"aliases":["AZL-109326","BELL-CVE-2026-98735","DEBIAN-CVE-2026-98735","GHSA-h7jm-4xpc-fcgr","UBUNTU-CVE-2026-98735"],"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 Bluetooth","requires_auth":"none","summary":"A use-after-free in the Linux kernel Bluetooth subsystem allows attackers to cause denial of service or execute code via race conditions during channel deletion.","user_interaction":"not_required","vuln_class":"use_after_free"},"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: hci_core: Serialize ACL scheduling with channel deletion\n\nhci_chan_sent() selects a channel under RCU but drops the read lock before\naccessing chan-\u003econn and returning the channel. The ACL and LE schedulers\nthen use its packet queue and update its transmit counters without any\nprotection against channel deletion.\n\nAfter TX selects a channel and releases RCU, a disconnect command timeout\non the separate request workqueue can run hci_conn_failed() and\nl2cap_conn_del(). hci_chan_del() can then unlink the channel, complete\nsynchronize_rcu(), purge its queue and free it before TX resumes. This\ncauses use-after-free both in hci_chan_sent() and in its callers.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0\n  Workqueue: hci0 hci_tx_work\n  Call Trace:\n   hci_chan_sent+0x892/0x9b0\n   hci_tx_work+0x5e6/0xb70\n  Allocated by task 91:\n   hci_chan_create+0xe3/0x350\n   l2cap_conn_add.part.0+0x12/0xa30\n   l2cap_chan_connect+0x110d/0x1b60\n   l2cap_sock_connect+0x310/0x530\n  Freed by task 99:\n   hci_chan_del+0x11f/0x170\n   l2cap_conn_del+0x4f1/0x800\n   l2cap_connect_cfm+0x88c/0xd30\n   hci_conn_failed+0x150/0x250\n   hci_abort_conn_sync+0x3e3/0x800\n   hci_cmd_sync_run+0x7e/0xc0\n   hci_abort_conn+0x105/0x1f0\n   disconnect_sync+0x157/0x290\n   hci_cmd_sync_work+0x13c/0x290\n\nHold the existing device mutex across channel selection and transmission\nin both schedulers to serialize them with channel teardown. Keep timeout\nhandling outside the critical sections because hci_link_tx_to() acquires\nthe same mutex. This also permits the transmit path to sleep, unlike\nextending the RCU read-side critical section across packet submission.","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: hci_core: Serialize ACL scheduling with channel deletion","id":"CVE-2026-98735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Bluetooth: hci_conn: Lock parent access during enhanced SCO setup","id":"CVE-2026-98736"},"packages":[],"prev":{"headline":"Bluetooth: hci_core: Serialize SCO and ISO scheduling with teardown","id":"CVE-2026-98734"},"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 use-after-free in the Linux kernel Bluetooth subsystem allows attackers to cause denial of service or execute code via race conditions during channel deletion.","url":"https://insights.sbomify.com/CVE-2026-98735/"}