Answer in brief
CVE-2023-54214 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix potential 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-2023-54214 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix potential 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.
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 | >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <b2fde8cb2a25125111f2144604e0e7c0ebcc4bba || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <60aaccf16d1e099c16bebfb96428ae762cb528f7 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <b8ed41cc04fb74005aa51d17865ca3d022760335 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <31a288a4df7f6a28e65da22a4ab2add4a963738e || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <64e28ecf44e46de9f01915a4146706a21c3469d2 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <994e3e18908f5c4a12d07b44018e6aa85f071048 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <df5703348813235874d851934e957c3723d71644 | b2fde8cb2a25125111f2144604e0e7c0ebcc4bba, a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49, 60aaccf16d1e099c16bebfb96428ae762cb528f7, b8ed41cc04fb74005aa51d17865ca3d022760335, 31a288a4df7f6a28e65da22a4ab2add4a963738e, 64e28ecf44e46de9f01915a4146706a21c3469d2, 994e3e18908f5c4a12d07b44018e6aa85f071048, df5703348813235874d851934e957c3723d71644 |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Dec 30, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix potential user-after-free This fixes all instances of which requires to allocate a buffer calling alloc_skb which may release the chan lock and reacquire later which makes it possible that the chan is disconnected in the meantime.
Quoted source text, attributed separately from HOL analysis.
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 | >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <b2fde8cb2a25125111f2144604e0e7c0ebcc4bba || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <60aaccf16d1e099c16bebfb96428ae762cb528f7 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <b8ed41cc04fb74005aa51d17865ca3d022760335 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <31a288a4df7f6a28e65da22a4ab2add4a963738e || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <64e28ecf44e46de9f01915a4146706a21c3469d2 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <994e3e18908f5c4a12d07b44018e6aa85f071048 || >=a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 <df5703348813235874d851934e957c3723d71644 | b2fde8cb2a25125111f2144604e0e7c0ebcc4bba, a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49, 60aaccf16d1e099c16bebfb96428ae762cb528f7, b8ed41cc04fb74005aa51d17865ca3d022760335, 31a288a4df7f6a28e65da22a4ab2add4a963738e, 64e28ecf44e46de9f01915a4146706a21c3469d2, 994e3e18908f5c4a12d07b44018e6aa85f071048, df5703348813235874d851934e957c3723d71644 |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Dec 30, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix potential user-after-free This fixes all instances of which requires to allocate a buffer calling alloc_skb which may release the chan lock and reacquire later which makes it possible that the chan is disconnected in the meantime.
Quoted source text, attributed separately from HOL analysis.