Answer in brief
CVE-2022-50386 records a High severity (CVSS 8.8) vulnerability in Bluetooth: L2CAP: Fix user-after-free. 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.
Answer in brief
CVE-2022-50386 records a High severity (CVSS 8.8) vulnerability in Bluetooth: L2CAP: Fix user-after-free. 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.
CVSS is 8.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3df91ea20e744344100b10ae69a17211fcf5b207 <11e40d6c0823f699d8ad501e48d1c3ae4be386cd || >=3df91ea20e744344100b10ae69a17211fcf5b207 <843fc4e386dd84b806a7f07fb062d8c3a44e5364 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <d91fc2836562f299f34e361e089e9fe154da4f73 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <7d6f9cb24d2b2f6b6370eac074e2e6b1bafdad45 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <0c108cf3ad386e0084277093b55a351c49e0be27 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <d1e894f950ad48897d1a7cb05909ea29d8c3810e || >=3df91ea20e744344100b10ae69a17211fcf5b207 <6ffde6e03085874ae22263ff4cef4869f797e84f || >=3df91ea20e744344100b10ae69a17211fcf5b207 <15fc21695eb606bdc5d483b92118ee42610a952d || >=3df91ea20e744344100b10ae69a17211fcf5b207 <35fcbc4243aad7e7d020b7c1dfb14bb888b20a4f | 11e40d6c0823f699d8ad501e48d1c3ae4be386cd, 843fc4e386dd84b806a7f07fb062d8c3a44e5364, d91fc2836562f299f34e361e089e9fe154da4f73, 7d6f9cb24d2b2f6b6370eac074e2e6b1bafdad45, 0c108cf3ad386e0084277093b55a351c49e0be27, d1e894f950ad48897d1a7cb05909ea29d8c3810e, 6ffde6e03085874ae22263ff4cef4869f797e84f, 15fc21695eb606bdc5d483b92118ee42610a952d, 35fcbc4243aad7e7d020b7c1dfb14bb888b20a4f |
| Linux/Linuxgeneric | 3.4 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct kref *kref) Bluetooth: chan 0000000023c4974d Bluetooth: parent 00000000ae861c08 ================================================================== BUG: KASAN: use-after-free in __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in __mutex_lock_common kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in __mutex_lock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task kworker/u3:2/389
Quoted source text, attributed separately from HOL analysis.
CVSS is 8.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3df91ea20e744344100b10ae69a17211fcf5b207 <11e40d6c0823f699d8ad501e48d1c3ae4be386cd || >=3df91ea20e744344100b10ae69a17211fcf5b207 <843fc4e386dd84b806a7f07fb062d8c3a44e5364 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <d91fc2836562f299f34e361e089e9fe154da4f73 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <7d6f9cb24d2b2f6b6370eac074e2e6b1bafdad45 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <0c108cf3ad386e0084277093b55a351c49e0be27 || >=3df91ea20e744344100b10ae69a17211fcf5b207 <d1e894f950ad48897d1a7cb05909ea29d8c3810e || >=3df91ea20e744344100b10ae69a17211fcf5b207 <6ffde6e03085874ae22263ff4cef4869f797e84f || >=3df91ea20e744344100b10ae69a17211fcf5b207 <15fc21695eb606bdc5d483b92118ee42610a952d || >=3df91ea20e744344100b10ae69a17211fcf5b207 <35fcbc4243aad7e7d020b7c1dfb14bb888b20a4f | 11e40d6c0823f699d8ad501e48d1c3ae4be386cd, 843fc4e386dd84b806a7f07fb062d8c3a44e5364, d91fc2836562f299f34e361e089e9fe154da4f73, 7d6f9cb24d2b2f6b6370eac074e2e6b1bafdad45, 0c108cf3ad386e0084277093b55a351c49e0be27, d1e894f950ad48897d1a7cb05909ea29d8c3810e, 6ffde6e03085874ae22263ff4cef4869f797e84f, 15fc21695eb606bdc5d483b92118ee42610a952d, 35fcbc4243aad7e7d020b7c1dfb14bb888b20a4f |
| Linux/Linuxgeneric | 3.4 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct kref *kref) Bluetooth: chan 0000000023c4974d Bluetooth: parent 00000000ae861c08 ================================================================== BUG: KASAN: use-after-free in __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in __mutex_lock_common kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in __mutex_lock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task kworker/u3:2/389
Quoted source text, attributed separately from HOL analysis.