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

CVE-2023-53827

Linux

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about to be destroyed.

CVSS
8.8
EPSS
0.34%
26.8% percentile
CISA KEV
Not listed
Published
2025.12.10
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about to be destroyed.

Affected product and versions

Product
Linux
Affected versions
>= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < f2d38e77aa5f3effc143e7dd24da8acf02925958, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < 1351551aa9058e07a20a27a158270cf84fcde621, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < c02421992505c95c7f3c9ad59ee35e22eac60988, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < d9ba36c22a7bb09d6bac4cc2f243eff05da53f43, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < ac6725a634f7e8c0330610a8527f20c730b61115, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < 348d446762e7c70778df8bafbdf3fa0df2123f58, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < d82a439c3cfdb28aa7e82e2e849c5c4dd9fca284, >= 61d6ef3e3408cdf7e622646fb90a9f7f9560b943 < a2a9339e1c9deb7e1e079e12e27a0265aea8421a, >= 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