Bug 2395681 (CVE-2023-53297) - CVE-2023-53297 kernel: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
Summary: CVE-2023-53297 kernel: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_di...
Keywords:
Status: NEW
Alias: CVE-2023-53297
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-16 09:03 UTC by OSIDB Bzimport
Modified: 2025-10-27 09:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:19102 0 None None None 2025-10-27 09:38:15 UTC
Red Hat Product Errata RHSA-2025:19103 0 None None None 2025-10-27 09:36:13 UTC

Description OSIDB Bzimport 2025-09-16 09:03:07 UTC
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp

conn->chan_lock isn't acquired before l2cap_get_chan_by_scid,
if l2cap_get_chan_by_scid returns NULL, then 'bad unlock balance'
is triggered.

Comment 6 errata-xmlrpc 2025-10-27 09:36:12 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:19103 https://access.redhat.com/errata/RHSA-2025:19103

Comment 7 errata-xmlrpc 2025-10-27 09:38:14 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:19102 https://access.redhat.com/errata/RHSA-2025:19102


Note You need to log in before you can comment on or make changes to this bug.