Answer in brief
CVE-2026-64557 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb(). 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 | >=8ffb929098a56939ac71509302eeab5b207bf262 <b39298044e5534612511a2ff5de03ba5f6e7a820 || >=8ffb929098a56939ac71509302eeab5b207bf262 <8c37e4338c801ebb8cee52436c01c41e009f6e87 || >=8ffb929098a56939ac71509302eeab5b207bf262 <84e718b6a814edc84159361f9f454a4e92ae91ae || >=8ffb929098a56939ac71509302eeab5b207bf262 <36da806f7fbaee56ad9e81859deec203f9728700 || >=8ffb929098a56939ac71509302eeab5b207bf262 <733e76e74e406c1d1ddc7369420dd8a47f48bb8a || >=8ffb929098a56939ac71509302eeab5b207bf262 <6fef032af0092ed5ccb767239a9ac1bc38c08a40 | b39298044e5534612511a2ff5de03ba5f6e7a820, 8c37e4338c801ebb8cee52436c01c41e009f6e87, 84e718b6a814edc84159361f9f454a4e92ae91ae, 36da806f7fbaee56ad9e81859deec203f9728700, 733e76e74e406c1d1ddc7369420dd8a47f48bb8a, 6fef032af0092ed5ccb767239a9ac1bc38c08a40 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 29, 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: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb() l2cap_sock_new_connection_cb() returned l2cap_pi(sk)->chan after release_sock(parent). Once the parent lock is dropped the newly enqueued child socket sk is reachable via the accept queue, so another task can accept and free it before the callback dereferences sk, resulting in a use-after-free. Rework the ->new_connection() op so the core, rather than the callback, owns the child channel's lifetime. The op now receives a pre-allocated new_chan and returns an errno instead of allocating and returning a channel. l2cap_new_connection() allocates the child channel and links it into the conn list via __l2cap_chan_add() before invoking the callback, so the conn-list reference keeps the channel alive once release_sock(parent) exposes the socket to other tasks. Channel configuration that was duplicated in l2cap_sock_init() and the various new_connection callbacks is consolidated into l2cap_chan_set_defaults(), which now inherits from the parent channel when one is supplied.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64557 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb(). 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 | >=8ffb929098a56939ac71509302eeab5b207bf262 <b39298044e5534612511a2ff5de03ba5f6e7a820 || >=8ffb929098a56939ac71509302eeab5b207bf262 <8c37e4338c801ebb8cee52436c01c41e009f6e87 || >=8ffb929098a56939ac71509302eeab5b207bf262 <84e718b6a814edc84159361f9f454a4e92ae91ae || >=8ffb929098a56939ac71509302eeab5b207bf262 <36da806f7fbaee56ad9e81859deec203f9728700 || >=8ffb929098a56939ac71509302eeab5b207bf262 <733e76e74e406c1d1ddc7369420dd8a47f48bb8a || >=8ffb929098a56939ac71509302eeab5b207bf262 <6fef032af0092ed5ccb767239a9ac1bc38c08a40 | b39298044e5534612511a2ff5de03ba5f6e7a820, 8c37e4338c801ebb8cee52436c01c41e009f6e87, 84e718b6a814edc84159361f9f454a4e92ae91ae, 36da806f7fbaee56ad9e81859deec203f9728700, 733e76e74e406c1d1ddc7369420dd8a47f48bb8a, 6fef032af0092ed5ccb767239a9ac1bc38c08a40 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 29, 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: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb() l2cap_sock_new_connection_cb() returned l2cap_pi(sk)->chan after release_sock(parent). Once the parent lock is dropped the newly enqueued child socket sk is reachable via the accept queue, so another task can accept and free it before the callback dereferences sk, resulting in a use-after-free. Rework the ->new_connection() op so the core, rather than the callback, owns the child channel's lifetime. The op now receives a pre-allocated new_chan and returns an errno instead of allocating and returning a channel. l2cap_new_connection() allocates the child channel and links it into the conn list via __l2cap_chan_add() before invoking the callback, so the conn-list reference keeps the channel alive once release_sock(parent) exposes the socket to other tasks. Channel configuration that was duplicated in l2cap_sock_init() and the various new_connection callbacks is consolidated into l2cap_chan_set_defaults(), which now inherits from the parent channel when one is supplied.
Quoted source text, attributed separately from HOL analysis.