Bug 2334503 (CVE-2024-56605) - CVE-2024-56605 kernel: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
Summary: CVE-2024-56605 kernel: Bluetooth: L2CAP: do not leave dangling sk pointer on ...
Keywords:
Status: NEW
Alias: CVE-2024-56605
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: 2024-12-27 15:06 UTC by OSIDB Bzimport
Modified: 2025-05-13 08:37 UTC (History)
4 users (show)

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:6966 0 None None None 2025-05-13 08:37:44 UTC

Description OSIDB Bzimport 2024-12-27 15:06:17 UTC 
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()

bt_sock_alloc() allocates the sk object and attaches it to the provided
sock object. On error l2cap_sock_alloc() frees the sk object, but the
dangling pointer is still attached to the sock object, which may create
use-after-free in other code.
Comment 1 Avinash Hanwate 2024-12-28 05:01:29 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56605-d424@gregkh/T
Comment 4 errata-xmlrpc 2025-05-13 08:37:43 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

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