Answer in brief
CVE-2026-63945 records a Unknown severity vulnerability in Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock. 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 <d9cbf7144ec589a3f0cc91f74a1a1af2d2b14afa || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <35f68f36d9883d56dec21cf85f7556d4657fc393 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <996c2104d0726a8fe584f85b3d6327197374a348 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <bc08c15746f25f41dd0508b25780d1e84acbb2ef || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <51cb9dcfdf9a1bccf312ab2ae4b62db629f7dcd5 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <4b5f8e608749b7e8fa386c6e4301cf9272595859 | d9cbf7144ec589a3f0cc91f74a1a1af2d2b14afa, 35f68f36d9883d56dec21cf85f7556d4657fc393, 996c2104d0726a8fe584f85b3d6327197374a348, bc08c15746f25f41dd0508b25780d1e84acbb2ef, 51cb9dcfdf9a1bccf312ab2ae4b62db629f7dcd5, 4b5f8e608749b7e8fa386c6e4301cf9272595859 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock iso_sock_close() calls iso_sock_clear_timer() before acquiring lock_sock(sk). iso_sock_clear_timer() reads iso_pi(sk)->conn twice without the socket lock held: if (!iso_pi(sk)->conn) return; cancel_delayed_work(&iso_pi(sk)->conn->timeout_work); Concurrently, iso_conn_del() executes under lock_sock(sk) and calls iso_chan_del(), which sets iso_pi(sk)->conn to NULL and may result in the final reference to the connection being dropped: CPU0 CPU1 ---- ---- iso_sock_clear_timer() if (conn != NULL) ... lock_sock(sk) iso_chan_del() iso_pi(sk)->conn = NULL cancel_delayed_work(conn) /* NULL deref or UAF */ iso_pi(sk)->conn is not stable across the unlock window, causing a NULL pointer dereference or use-after-free. Serialize iso_sock_clear_timer() with the socket lock by moving it inside lock_sock()/release_sock(), matching the pattern used in iso_conn_del() and all other call sites.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-63945 records a Unknown severity vulnerability in Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock. 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 <d9cbf7144ec589a3f0cc91f74a1a1af2d2b14afa || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <35f68f36d9883d56dec21cf85f7556d4657fc393 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <996c2104d0726a8fe584f85b3d6327197374a348 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <bc08c15746f25f41dd0508b25780d1e84acbb2ef || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <51cb9dcfdf9a1bccf312ab2ae4b62db629f7dcd5 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <4b5f8e608749b7e8fa386c6e4301cf9272595859 | d9cbf7144ec589a3f0cc91f74a1a1af2d2b14afa, 35f68f36d9883d56dec21cf85f7556d4657fc393, 996c2104d0726a8fe584f85b3d6327197374a348, bc08c15746f25f41dd0508b25780d1e84acbb2ef, 51cb9dcfdf9a1bccf312ab2ae4b62db629f7dcd5, 4b5f8e608749b7e8fa386c6e4301cf9272595859 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock iso_sock_close() calls iso_sock_clear_timer() before acquiring lock_sock(sk). iso_sock_clear_timer() reads iso_pi(sk)->conn twice without the socket lock held: if (!iso_pi(sk)->conn) return; cancel_delayed_work(&iso_pi(sk)->conn->timeout_work); Concurrently, iso_conn_del() executes under lock_sock(sk) and calls iso_chan_del(), which sets iso_pi(sk)->conn to NULL and may result in the final reference to the connection being dropped: CPU0 CPU1 ---- ---- iso_sock_clear_timer() if (conn != NULL) ... lock_sock(sk) iso_chan_del() iso_pi(sk)->conn = NULL cancel_delayed_work(conn) /* NULL deref or UAF */ iso_pi(sk)->conn is not stable across the unlock window, causing a NULL pointer dereference or use-after-free. Serialize iso_sock_clear_timer() with the socket lock by moving it inside lock_sock()/release_sock(), matching the pattern used in iso_conn_del() and all other call sites.
Quoted source text, attributed separately from HOL analysis.