Bluetooth: ISO: fix leaking sk after socket release
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix leaking sk after socket release iso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || sock_flag(sk, SOCK_DEAD) for early return, but this is always true since sock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket always leaks, iso_sock_destruct is never called. The socket reference also leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping. Fix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for something else, and lock_sock to ensure iso_sock_kill() puts sk only after socket release only once. Release and iso_conn_del may run concurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up after zapping. Remove call to iso_sock_kill() from iso_sock_close(), as it's generally no-op there.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.103, 6.18.44, 7.1.8
- CVEs
- CVE-2026-74536
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 14:50 UTC · Revision 1
Source evidence
Bluetooth: ISO: fix leaking sk after socket release
core-osv · Original sourcePublished 15 Aug 2026, 12:27 UTC
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix leaking sk after socket release iso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || sock_flag(sk, SOCK_DEAD) for early return, but this is always true since sock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket always leaks, iso_sock_destruct is never called. The socket reference also leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping. Fix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for something else, and lock_sock to ensure iso_sock_kill() puts sk only after socket release only once. Release and iso_conn_del may run concurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up after zapping. Remove call to iso_sock_kill() from iso_sock_close(), as it's generally no-op there.
osv:CVE-2026-74536
Kernel
Fixed versions: 6.12.103, 6.18.44, 7.1.8
Complete source record
{
"id": "eeb876a352fa9ed551509f81196f3b0f72f68ed3b4d7a321f438c753f3492cab",
"url": "https://osv.dev/vulnerability/CVE-2026-74536",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: ISO: fix leaking sk after socket release",
"summary": "In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix leaking sk after socket release iso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || sock_flag(sk, SOCK_DEAD) for early return, but this is always true since sock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket always leaks, iso_sock_destruct is never called. The socket reference also leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping. Fix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for something else, and lock_sock to ensure iso_sock_kill() puts sk only after socket release only once. Release and iso_conn_del may run concurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up after zapping. Remove call to iso_sock_kill() from iso_sock_close(), as it's generally no-op there.",
"evidence": "osv:CVE-2026-74536",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.44",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-74536",
"aliases": [
"CVE-2026-74536"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ccf74f2390d60a2f9a75ef496d2564abb478f46a"
},
{
"fixed": "96ed3c772c08e7a91c399567f412618e43231023"
},
{
"fixed": "e76a0ae6542ae43241b2147bacf4990e7ae5316a"
},
{
"fixed": "e30e5ca63c8fbe3cd505fbb419bb547760cda633"
},
{
"fixed": "ce57442a379212fe3fda59c9437ee8217eceb5b1"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74536.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.12.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74536.json"
}
}
],
"modified": "2026-10-28T02:30:51.392039240Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/96ed3c772c08e7a91c399567f412618e43231023",
"https://git.kernel.org/stable/c/ce57442a379212fe3fda59c9437ee8217eceb5b1",
"https://git.kernel.org/stable/c/e30e5ca63c8fbe3cd505fbb419bb547760cda633",
"https://git.kernel.org/stable/c/e76a0ae6542ae43241b2147bacf4990e7ae5316a",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74536.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-74536",
"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/74xxx/CVE-2026-74536.json"
}
},
"related_cves": [
{
"value": "CVE-2026-74536",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 519687,
"published_at": "2026-08-15T12:27:49.054+00:00"
}