{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82388 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82388 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82388 is a medium-severity vulnerability in zephyrproject zephyr, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-82388 and fix it if it is affected.\n\nWhat it is: CVE-2026-82388 is a medium-severity vulnerability in zephyrproject zephyr, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-82388 in the wild and no public exploit code.\n\nAffected product: zephyrproject zephyr. 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-82388/ (Markdown: https://insights.sbomify.com/CVE-2026-82388/index.md)","id":"CVE-2026-82388","markdown":"https://insights.sbomify.com/CVE-2026-82388/index.md","name":"CVE-2026-82388","record":{"aliases":["GHSA-398x-f7rq-5jj9","UBUNTU-CVE-2026-82388"],"analysis":null,"analysis_generated_by":null,"assigner":"zephyr","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"bt_hfp_hf_connect() in subsys/bluetooth/host/classic/hfp_hf.c allocates the per-connection HFP Hands-Free object with hfp_hf_create(), which starts an SDP discovery by passing the object's embedded hf-\u003esdp_param to bt_sdp_discover(). That call links the caller-owned parameter block into the SDP client's request list (session-\u003ereqs in subsys/bluetooth/host/classic/sdp.c). If the subsequent bt_rfcomm_dlc_connect() then failed, the affected code wiped the entire object with (void)memset(new_hf, 0, sizeof(*new_hf)) while that discovery was still outstanding, zeroing the sys_snode_t _node that is still linked in the SDP client's list along with the request's func, uuid and pool pointers, and zeroing the hf-\u003eslc_work work item that may already be queued on the system workqueue. The discovery could not be retracted instead: bt_sdp_discover_cancel() is declared in include/zephyr/bluetooth/classic/sdp.h but has no implementation.\n\nThe failing branch is reachable with peer-supplied input. The documented use of bt_hfp_hf_connect() is to pass the RFCOMM channel read out of the remote Audio Gateway's SDP record; neither bt_sdp_get_proto_param() nor bt_hfp_hf_connect() range-checks that value, so a remote device advertising an HFP AG record with an RFCOMM channel outside 1-30 makes bt_rfcomm_dlc_connect() return -EINVAL and drives the local device into the wipe. The same branch is reached without any application misuse when the remote peer controls connection timing, for example when the RFCOMM session is in BT_RFCOMM_STATE_DISCONNECTING or the ACL is dropped between object creation and the RFCOMM call.\n\nOnce the object has been wiped, the Bluetooth host continues to use it: sdp_client_alloc_buf() dereferences session-\u003eparam-\u003epool, which is now NULL, and the SDP receive paths call session-\u003eparam-\u003efunc() through a null function pointer, neither of which is NULL-checked. Because the wipe also clears hf-\u003eacl, the pool slot is considered free and a retry or an incoming HFP connection re-appends the same still-linked list node, turning session-\u003ereqs into a self-referential list that the host's list walkers never leave. The result is a fault or an unrecoverable hang in the Bluetooth host thread; the stray indirect call is through an all-zero pointer whose target the attacker does not control, so the practical impact is denial of service.\n\nThe fix keeps the object allocated and marks it with a new BT_HFP_HF_FLAG_RELEASING flag, letting bt_hfp_hf_discover_cb() release it once the discovery completes instead of destroying it under the SDP client. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_HFP_HF enabled are affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Use of a released HFP HF object after a failed RFCOMM connect in the Bluetooth Classic host","id":"CVE-2026-82388","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"In the Bluetooth Classic Hands-Free Profile Audio Gateway role, hfp_ag_create() in subsys/bluetooth/host/classic/hfp_ag.c starts an SDP disc","id":"CVE-2026-82389"},"packages":[],"prev":{"headline":"Apache Roller: Stored cross-site scripting via uploaded media content type","id":"CVE-2026-82387"},"products":["zephyr"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["zephyrproject"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-82388/"}