Bluetooth: ISO: release unused CIS holds after channel attach
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: release unused CIS holds after channel attach hci_bind_cis() and hci_connect_cis() return one hci_conn hold for the ISO layer. A new channel association consumes that hold, which is eventually released by iso_conn_free(). There are two cases where iso_chan_add() does not create an association: it returns success when the socket is already attached to the same iso_conn, and it returns -EBUSY when another socket is attached. The hold returned for the current call is unused in both cases. This occurs when deferred setup calls iso_connect_cis() again for its existing socket, or when another socket attempts to reuse the CIS. Detect the idempotent case while the connection is locked and release the unused hold after iso_chan_add(). Also release it on -EBUSY. Do not drop it for other errors: a newly allocated iso_conn releases the transferred hold when its last temporary reference is put.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.113, 6.18.55, 7.2.9
- CVEs
- CVE-2026-98458
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:34 UTC · Revision 1
Source evidence
Bluetooth: ISO: release unused CIS holds after channel attach
core-osv · Original sourcePublished 18 Oct 2026, 15:15 UTC
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: release unused CIS holds after channel attach hci_bind_cis() and hci_connect_cis() return one hci_conn hold for the ISO layer. A new channel association consumes that hold, which is eventually released by iso_conn_free(). There are two cases where iso_chan_add() does not create an association: it returns success when the socket is already attached to the same iso_conn, and it returns -EBUSY when another socket is attached. The hold returned for the current call is unused in both cases. This occurs when deferred setup calls iso_connect_cis() again for its existing socket, or when another socket attempts to reuse the CIS. Detect the idempotent case while the connection is locked and release the unused hold after iso_chan_add(). Also release it on -EBUSY. Do not drop it for other errors: a newly allocated iso_conn releases the transferred hold when its last temporary reference is put.
osv:CVE-2026-98458
Kernel
Fixed versions: 6.12.113, 6.18.55, 7.2.9
Complete source record
{
"id": "112e9ae3aedc122f2fde599129c6ed6d739a73d8720a6788b0788c924fa83a35",
"url": "https://osv.dev/vulnerability/CVE-2026-98458",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: ISO: release unused CIS holds after channel attach",
"summary": "In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: release unused CIS holds after channel attach hci_bind_cis() and hci_connect_cis() return one hci_conn hold for the ISO layer. A new channel association consumes that hold, which is eventually released by iso_conn_free(). There are two cases where iso_chan_add() does not create an association: it returns success when the socket is already attached to the same iso_conn, and it returns -EBUSY when another socket is attached. The hold returned for the current call is unused in both cases. This occurs when deferred setup calls iso_connect_cis() again for its existing socket, or when another socket attempts to reuse the CIS. Detect the idempotent case while the connection is locked and release the unused hold after iso_chan_add(). Also release it on -EBUSY. Do not drop it for other errors: a newly allocated iso_conn releases the transferred hold when its last temporary reference is put.",
"evidence": "osv:CVE-2026-98458",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.113",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.55",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98458",
"aliases": [
"CVE-2026-98458"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "69997d50ec574be816b4ee8f9cee52ebbd53f8bd"
},
{
"fixed": "e0e8b70207eaf27aee0a05ec5bf2d1b6bcb004d1"
},
{
"fixed": "ed4c026cc4094dfb7a329b9d8df0ddd0be1b2458"
},
{
"fixed": "e5fcca51177f224604e3a8c926ffd5edbeb58b09"
},
{
"fixed": "0fcd4dad555c96e0bd3a1b8c569f989be85c7341"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98458.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.6.0"
},
{
"fixed": "6.12.113"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.55"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98458.json"
}
}
],
"modified": "2026-10-28T02:30:52.254472974Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0fcd4dad555c96e0bd3a1b8c569f989be85c7341",
"https://git.kernel.org/stable/c/e0e8b70207eaf27aee0a05ec5bf2d1b6bcb004d1",
"https://git.kernel.org/stable/c/e5fcca51177f224604e3a8c926ffd5edbeb58b09",
"https://git.kernel.org/stable/c/ed4c026cc4094dfb7a329b9d8df0ddd0be1b2458",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98458.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98458",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98458.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98458",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521005,
"published_at": "2026-10-18T15:15:07.572+00:00"
}