SECUFOCUSNOW
Home›CVE index›CVE-2023-54214
Review reviewHigh

CVE-2023-54214

Linux

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.

CVSS
8.8
EPSS
0.27%
19.6% percentile
CISA KEV
Not listed
Published
2025.12.30
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.27%
Technical severityCVSS 8.8

Vulnerability overview

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.

Affected product and versions

Product
Linux
Affected versions
>= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < b2fde8cb2a25125111f2144604e0e7c0ebcc4bba, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < 60aaccf16d1e099c16bebfb96428ae762cb528f7, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < b8ed41cc04fb74005aa51d17865ca3d022760335, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < 31a288a4df7f6a28e65da22a4ab2add4a963738e, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < 64e28ecf44e46de9f01915a4146706a21c3469d2, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < 994e3e18908f5c4a12d07b44018e6aa85f071048, >= a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 < df5703348813235874d851934e957c3723d71644, >= 3.5
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available