linux-cve-announce - CVE-2023-53016: Bluetooth: Fix possible deadlock in rfcomm_sk_state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025032716-CVE-2023-53016-f30c@gregkh>
Date: Thu, 27 Mar 2025 17:44:03 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-53016: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: Fix possible deadlock in rfcomm_sk_state_change

syzbot reports a possible deadlock in rfcomm_sk_state_change [1].
While rfcomm_sock_connect acquires the sk lock and waits for
the rfcomm lock, rfcomm_sock_release could have the rfcomm
lock and hit a deadlock for acquiring the sk lock.
Here's a simplified flow:

rfcomm_sock_connect:
  lock_sock(sk)
  rfcomm_dlc_open:
    rfcomm_lock()

rfcomm_sock_release:
  rfcomm_sock_shutdown:
    rfcomm_lock()
    __rfcomm_dlc_close:
        rfcomm_k_state_change:
	  lock_sock(sk)

This patch drops the sk lock before calling rfcomm_dlc_open to
avoid the possible deadlock and holds sk's reference count to
prevent use-after-free after rfcomm_dlc_open completes.

The Linux kernel CVE team has assigned CVE-2023-53016 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.15 with commit 1804fdf6e494e5e2938c65d8391690b59bcff897 and fixed in 5.15.91 with commit 98aec50ff7f60cc6f2d6a4396b475c547e58b04d
	Issue introduced in 5.15 with commit 1804fdf6e494e5e2938c65d8391690b59bcff897 and fixed in 6.1.9 with commit 17511bd84871f4a6106cb335616e086880313f3f
	Issue introduced in 5.15 with commit 1804fdf6e494e5e2938c65d8391690b59bcff897 and fixed in 6.2 with commit 1d80d57ffcb55488f0ec0b77928d4f82d16b6a90

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-2023-53016
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/rfcomm/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/98aec50ff7f60cc6f2d6a4396b475c547e58b04d
	https://git.kernel.org/stable/c/17511bd84871f4a6106cb335616e086880313f3f
	https://git.kernel.org/stable/c/1d80d57ffcb55488f0ec0b77928d4f82d16b6a90