{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98632 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98632 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-98632 and fix it if it is affected.\n\nWhat it is: CVE-2026-98632 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-98632 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-98632/ (Markdown: https://insights.sbomify.com/CVE-2026-98632/index.md)","id":"CVE-2026-98632","markdown":"https://insights.sbomify.com/CVE-2026-98632/index.md","name":"CVE-2026-98632","record":{"aliases":["AZL-108921","BELL-CVE-2026-98632","DEBIAN-CVE-2026-98632","GHSA-qvq7-5mpj-hvwr","UBUNTU-CVE-2026-98632"],"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 mesh subsystem allows attackers to cause denial of service or execute arbitrary code via crafted Bluetooth transmissions.","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: mgmt: Dequeue pending mesh_send_sync entries on cancel\n\nIn send_cancel(), pending mesh_tx objects are removed from the\nhdev-\u003emesh_pending list and freed via mesh_send_complete().  However, if\na mesh transmission was already queued onto hdev-\u003ecmd_sync_work_list via\nmesh_next(), the queued entry retains a raw pointer to mesh_tx.\n\nWhen hci_cmd_sync_work later processes the entry, it attempts to execute\nmesh_send_sync and its destroy callback mesh_send_start_complete using\nthe already freed mesh_tx pointer, leading to a use-after-free.\n\nFix this by invoking hci_cmd_sync_dequeue() for mesh_send_sync on the\ntarget mesh_tx before completing it.  If the entry is found and dequeued,\nits destroy callback will complete and free the object; otherwise,\nmesh_send_complete() is called directly.\n\nAdditionally, ensure the transmission queue advances after cancellation\nor errors.  In mesh_send_start_complete(), call mesh_next() on error\nunless err is -ECANCELED, because hci_cmd_sync_dequeue() holds\nhdev-\u003ecmd_sync_work_lock and calling mesh_next() synchronously would\ndeadlock.  Instead, advance the queue in send_cancel() once the lock is\nreleased and if no transmission is in progress.","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: mgmt: Dequeue pending mesh_send_sync entries on cancel","id":"CVE-2026-98632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Bluetooth: btnxpuart: Fix skb leak in nxp_process_fw_dump()","id":"CVE-2026-98633"},"packages":[],"prev":{"headline":"xsk: Use a 32-bit compare in xsk_map_gen_lookup","id":"CVE-2026-98631"},"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 use-after-free in the Linux kernel Bluetooth mesh subsystem allows attackers to cause denial of service or execute arbitrary code via crafted Bluetooth transmissions.","url":"https://insights.sbomify.com/CVE-2026-98632/"}