Bug 2334495 (CVE-2024-56604) - CVE-2024-56604 kernel: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
Summary: CVE-2024-56604 kernel: Bluetooth: RFCOMM: avoid leaving dangling sk pointer i...
Keywords:
Status: NEW
Alias: CVE-2024-56604
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:05 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:41 UTC

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

Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()

bt_sock_alloc() attaches allocated sk object to the provided sock object.
If rfcomm_dlc_alloc() fails, we release the sk object, but leave the
dangling pointer in the sock object, which may cause use-after-free.

Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().
Comment 1 Avinash Hanwate 2024-12-28 05:32:30 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56604-8494@gregkh/T
Comment 2 errata-xmlrpc 2025-05-13 08:37:39 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.