[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024122704-CVE-2024-56605-d424@gregkh>
Date: Fri, 27 Dec 2024 15:51:12 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-56605: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
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.
The Linux kernel CVE team has assigned CVE-2024-56605 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.287 with commit f6ad641646b67f29c7578dcd6c25813c7dcbf51e
Fixed in 5.10.231 with commit daa13175a6dea312a76099066cb4cbd4fc959a84
Fixed in 5.15.174 with commit a8677028dd5123e5e525b8195483994d87123de4
Fixed in 6.1.120 with commit bb2f2342a6ddf7c04f9aefbbfe86104cd138e629
Fixed in 6.6.66 with commit 8ad09ddc63ace3950ac43db6fbfe25b40f589dd6
Fixed in 6.12.5 with commit 61686abc2f3c2c67822aa23ce6f160467ec83d35
Fixed in 6.13-rc1 with commit 7c4f78cdb8e7501e9f92d291a7d956591bf73be9
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-56605
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/bluetooth/l2cap_sock.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f6ad641646b67f29c7578dcd6c25813c7dcbf51e
https://git.kernel.org/stable/c/daa13175a6dea312a76099066cb4cbd4fc959a84
https://git.kernel.org/stable/c/a8677028dd5123e5e525b8195483994d87123de4
https://git.kernel.org/stable/c/bb2f2342a6ddf7c04f9aefbbfe86104cd138e629
https://git.kernel.org/stable/c/8ad09ddc63ace3950ac43db6fbfe25b40f589dd6
https://git.kernel.org/stable/c/61686abc2f3c2c67822aa23ce6f160467ec83d35
https://git.kernel.org/stable/c/7c4f78cdb8e7501e9f92d291a7d956591bf73be9
Powered by blists - more mailing lists