All reports
Medium

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

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-56605

Probability of exploitation in the next 30 days: 0.24%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in the Linux kernel's Bluetooth subsystem. During socket initialization, an error handling failure leaves behind a reference to freed memory. A local user could exploit this use-after-free condition to cause a denial of service (DoS) or potentially achieve privilege escalation.