UBUNTU-CVE-2026-82389 (CVE-2026-82389)
Vulnerability from osv_ubuntu – Published: 2026-10-26 17:17 – Updated: 2026-10-28 17:43 – Source websiteIn the Bluetooth Classic Hands-Free Profile Audio Gateway role, hfp_ag_create() in subsys/bluetooth/host/classic/hfp_ag.c starts an SDP discovery toward the peer, which links the embedded ag->sdp_param._node into the SDP client's pending request list in subsys/bluetooth/host/classic/sdp.c. If the subsequent bt_rfcomm_dlc_connect() call fails, bt_hfp_ag_connect() cleaned up by memset()-ing the entire AG object while that node was still linked, and while ag->slc_work could still be queued on the system work queue. An in-flight SDP discovery cannot be cancelled — bt_sdp_discover_cancel() is declared in the public header but has no implementation — so the request stays in the list with its func, pool and uuid pointers zeroed. The RFCOMM channel passed to bt_hfp_ag_connect() is taken from the peer's own SDP Hands-Free service record in the normal AG flow (bt_sdp_get_proto_param() performs no range validation, and samples/bluetooth/classic/handsfree_ag feeds the value straight through), so a remote BR/EDR device in radio range that advertises an RFCOMM channel outside the valid range 0x01..0x1e deterministically forces bt_rfcomm_dlc_connect() to fail and reach the wipe. Reading the peer's SDP record requires no pairing, and the peer can also trigger the failure by dropping the ACL or racing an RFCOMM DLC on the same DLCI at the right moment. When the SDP client next advances its request list, sdp_client_discover() dereferences the zeroed parameters — net_buf_alloc(param->pool, …) with a NULL pool and param->uuid->type — and the result-notification paths call through the NULL params->func. Zeroing a linked node also truncates the request list behind a stale tail pointer, and re-arming the freed AG slot re-appends the same node and can produce a self-looping list that hangs the Bluetooth RX thread. The impact is a crash or hang of the Bluetooth stack; the written value is a constant zero at a fixed static address, so no attacker-controlled write is available. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_HFP_AG that use the Audio Gateway role are affected.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1",
"3.1.2-1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build1",
"3.1.2-1build2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1.1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1.1",
"3.1.2-1.1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-4"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-4"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1.1build1",
"3.1.2-4"
]
}
],
"aliases": [],
"details": "In the Bluetooth Classic Hands-Free Profile Audio Gateway role, hfp_ag_create() in subsys/bluetooth/host/classic/hfp_ag.c starts an SDP discovery toward the peer, which links the embedded ag-\u003esdp_param._node into the SDP client\u0027s pending request list in subsys/bluetooth/host/classic/sdp.c. If the subsequent bt_rfcomm_dlc_connect() call fails, bt_hfp_ag_connect() cleaned up by memset()-ing the entire AG object while that node was still linked, and while ag-\u003eslc_work could still be queued on the system work queue. An in-flight SDP discovery cannot be cancelled \u2014 bt_sdp_discover_cancel() is declared in the public header but has no implementation \u2014 so the request stays in the list with its func, pool and uuid pointers zeroed. The RFCOMM channel passed to bt_hfp_ag_connect() is taken from the peer\u0027s own SDP Hands-Free service record in the normal AG flow (bt_sdp_get_proto_param() performs no range validation, and samples/bluetooth/classic/handsfree_ag feeds the value straight through), so a remote BR/EDR device in radio range that advertises an RFCOMM channel outside the valid range 0x01..0x1e deterministically forces bt_rfcomm_dlc_connect() to fail and reach the wipe. Reading the peer\u0027s SDP record requires no pairing, and the peer can also trigger the failure by dropping the ACL or racing an RFCOMM DLC on the same DLCI at the right moment. When the SDP client next advances its request list, sdp_client_discover() dereferences the zeroed parameters \u2014 net_buf_alloc(param-\u003epool, \u2026) with a NULL pool and param-\u003euuid-\u003etype \u2014 and the result-notification paths call through the NULL params-\u003efunc. Zeroing a linked node also truncates the request list behind a stale tail pointer, and re-arming the freed AG slot re-appends the same node and can produce a self-looping list that hangs the Bluetooth RX thread. The impact is a crash or hang of the Bluetooth stack; the written value is a constant zero at a fixed static address, so no attacker-controlled write is available. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_HFP_AG that use the Audio Gateway role are affected.",
"id": "UBUNTU-CVE-2026-82389",
"modified": "2026-10-28T17:43:52Z",
"published": "2026-10-26T17:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-82389"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82389"
},
{
"type": "REPORT",
"url": "https://github.com/zephyrproject-rtos/zephyr"
},
{
"type": "REPORT",
"url": "https://github.com/cveproject/cvelistv5/tree/main/cves/2026/82xxx/cve-2026-82389.json"
},
{
"type": "REPORT",
"url": "https://github.com/zephyrproject-rtos/zephyr/commit/18a3243b21ef6298988a3034dbda2704a7ad73a4"
},
{
"type": "REPORT",
"url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/ghsa-rrqj-542q-26jm"
},
{
"type": "REPORT",
"url": "https://nvd.nist.gov/vuln/detail/cve-2026-82389"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-82389"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.