{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98734 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98734 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-98734 and fix it if it is affected.\n\nWhat it is: CVE-2026-98734 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-98734 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-98734/ (Markdown: https://insights.sbomify.com/CVE-2026-98734/index.md)","id":"CVE-2026-98734","markdown":"https://insights.sbomify.com/CVE-2026-98734/index.md","name":"CVE-2026-98734","record":{"aliases":["AZL-109143","BELL-CVE-2026-98734","DEBIAN-CVE-2026-98734","GHSA-4q25-9c2v-7w4q","UBUNTU-CVE-2026-98734"],"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":"low_privilege","summary":"A use-after-free in the Linux kernel Bluetooth subsystem allows local attackers to execute code or cause a denial of service via race conditions during connection teardown.","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 SCO and ISO scheduling with teardown\n\nhci_low_sent() selects a connection under RCU but drops the read lock\nbefore calculating its quota and returning it to the scheduler. The\nconnection is then used without lifetime protection by hci_sched_iso()\nand hci_sched_sco().\n\nAfter the TX worker drops the RCU read lock, hci_abort_conn_sync() on\nhdev-\u003ereq_workqueue can remove the connection from the hash, complete\nsynchronize_rcu(), purge its queues and release it. The TX worker on\nhdev-\u003eworkqueue can then access the freed connection in hci_quote_sent()\nor while dequeuing packets and updating conn-\u003esent.\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in hci_low_sent+0x730/0x840\n  Workqueue: hci0 hci_tx_work\n  Call Trace:\n   hci_low_sent+0x730/0x840\n   hci_sched_iso+0x25e/0x4d0\n   hci_tx_work+0x239/0xcb0\n\n  Allocated by task 93:\n   __hci_conn_add+0x16f/0x1b40\n   hci_bind_bis+0x782/0x17b0\n   hci_connect_bis+0xa0/0x510\n   iso_sock_connect+0x589/0x1050\n\n  Freed by task 88:\n   kfree+0x131/0x3c0\n   device_release+0xc8/0x240\n   kobject_put+0x14d/0x280\n   hci_conn_del+0x55a/0xe80\n   hci_disconnect_sync+0x156/0x180\n   hci_abort_conn_sync+0x3e7/0x940\n   hci_cmd_sync_work+0x13c/0x290\n\nHold hci_dev_lock() across connection selection and transmission in both\nSCO and ISO scheduling, serializing them with connection teardown. This\nalso prevents queuing completion timestamps after the connection queues\nhave been purged. Extending RCU across transmission would be unsafe\nbecause the transmit path can sleep. Keep the ISO timeout check outside\nthe mutex since hci_link_tx_to() takes it itself.\n\nThe preceding channel fix already holds this mutex in the ACL and LE\nschedulers, which call the SCO scheduler between packets. Move the SCO\nbody to __hci_sched_sco(), assert that its caller holds the mutex, and\nuse it directly from these locked paths. Keep a locking hci_sched_sco()\nwrapper for the direct calls from hci_tx_work(). This avoids recursively\nacquiring the device mutex while preserving the scheduling order.\n\nRemove the obsolete claim that connection removal disables TX.","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 SCO and ISO scheduling with teardown","id":"CVE-2026-98734","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_core: Serialize ACL scheduling with channel deletion","id":"CVE-2026-98735"},"packages":[],"prev":{"headline":"Bluetooth: hci_core: Serialize fragmented ISO packet queueing","id":"CVE-2026-98733"},"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 local attackers to execute code or cause a denial of service via race conditions during connection teardown.","url":"https://insights.sbomify.com/CVE-2026-98734/"}