Answer in brief
CVE-2026-23461 records a High severity (CVSS 8.8) vulnerability in Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=efc30877bd4bc85fefe98d80af60fafc86e5775e <11a87dd5df428a4b79a84d2790cac7f3c73f1f0d || >=f87271d21dd4ee83857ca11b94e7b4952749bbae <c22a5e659959eb77c2fbb58a5adfaf3c3dab7abf || >=ab4eedb790cae44313759b50fe47da285e2519d5 <da3000cbe4851458a22be38bb18c0689c39fdd5f || >=ab4eedb790cae44313759b50fe47da285e2519d5 <71030f3b3015a412133a805ff47970cdcf30c2b8 || >=ab4eedb790cae44313759b50fe47da285e2519d5 <752a6c9596dd25efd6978a73ff21f3b592668f4a || 18ab6b6078fa8191ca30a3065d57bf35d5635761 || >=6.6.84 <6.6.130 || >=6.12.20 <6.12.78 || >=6.13.8 <6.14 | 11a87dd5df428a4b79a84d2790cac7f3c73f1f0d, c22a5e659959eb77c2fbb58a5adfaf3c3dab7abf, da3000cbe4851458a22be38bb18c0689c39fdd5f, 71030f3b3015a412133a805ff47970cdcf30c2b8, 752a6c9596dd25efd6978a73ff21f3b592668f4a, 6.6.130, 6.12.78, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hci_chan_del"), l2cap_conn_del() uses conn->lock to protect access to conn->users. However, l2cap_register_user() and l2cap_unregister_user() don't use conn->lock, creating a race condition where these functions can access conn->users and conn->hchan concurrently with l2cap_conn_del(). This can lead to use-after-free and list corruption bugs, as reported by syzbot. Fix this by changing l2cap_register_user() and l2cap_unregister_user() to use conn->lock instead of hci_dev_lock(), ensuring consistent locking for the l2cap_conn structure.
Quoted source text, attributed separately from HOL analysis.