Bug 2420376 (CVE-2023-53827) - CVE-2023-53827 kernel: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}
Summary: CVE-2023-53827 kernel: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconne...
Keywords:
Status: NEW
Alias: CVE-2023-53827
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-12-09 02:06 UTC by OSIDB Bzimport
Modified: 2026-02-26 04:22 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-2026:3360 0 None None None 2026-02-25 15:16:49 UTC
Red Hat Product Errata RHSA-2026:3388 0 None None None 2026-02-26 04:22:52 UTC

Description OSIDB Bzimport 2025-12-09 02:06:47 UTC 
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.
Comment 1 Alexander B 2025-12-09 15:09:09 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025120952-CVE-2023-53827-b045@gregkh/T
Comment 5 errata-xmlrpc 2026-02-25 15:16:48 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:3360 https://access.redhat.com/errata/RHSA-2026:3360
Comment 6 errata-xmlrpc 2026-02-26 04:22:51 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.2 Advanced Update Support

Via RHSA-2026:3388 https://access.redhat.com/errata/RHSA-2026:3388
Note You need to log in before you can comment on or make changes to this bug.