CVE-2024-56604
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.22%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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().
- CVSS 3.1
- 7.8 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.22% probability · 13th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-416
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/32df687e129ef0f9afcbcc914f7c32deb28fd481Patch
- https://git.kernel.org/stable/c/3945c799f12b8d1f49a3b48369ca494d981ac465Patch
- https://git.kernel.org/stable/c/6021ccc2471b7b95e29b7cfc7938e042bf56e281Patch
- https://git.kernel.org/stable/c/ac3eaac4cf142a15fe67be747a682b1416efeb6ePatch
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.