Answer in brief
CVE-2026-74536 records a Unknown severity vulnerability in Bluetooth: ISO: fix leaking sk after socket release. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <96ed3c772c08e7a91c399567f412618e43231023 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <e76a0ae6542ae43241b2147bacf4990e7ae5316a || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <e30e5ca63c8fbe3cd505fbb419bb547760cda633 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <ce57442a379212fe3fda59c9437ee8217eceb5b1 | 96ed3c772c08e7a91c399567f412618e43231023, e76a0ae6542ae43241b2147bacf4990e7ae5316a, e30e5ca63c8fbe3cd505fbb419bb547760cda633, ce57442a379212fe3fda59c9437ee8217eceb5b1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74536 records a Unknown severity vulnerability in Bluetooth: ISO: fix leaking sk after socket release. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <96ed3c772c08e7a91c399567f412618e43231023 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <e76a0ae6542ae43241b2147bacf4990e7ae5316a || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <e30e5ca63c8fbe3cd505fbb419bb547760cda633 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <ce57442a379212fe3fda59c9437ee8217eceb5b1 | 96ed3c772c08e7a91c399567f412618e43231023, e76a0ae6542ae43241b2147bacf4990e7ae5316a, e30e5ca63c8fbe3cd505fbb419bb547760cda633, ce57442a379212fe3fda59c9437ee8217eceb5b1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.