linux-cve-announce - CVE-2024-56654: Bluetooth: hci_event: Fix using rcu_read

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: <2024122749-CVE-2024-56654-66a1@gregkh>
Date: Fri, 27 Dec 2024 16:06:51 +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-56654: Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating

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

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

Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating

The usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is
not safe since for the most part entries fetched this way shall be
treated as rcu_dereference:

	Note that the value returned by rcu_dereference() is valid
	only within the enclosing RCU read-side critical section [1]_.
	For example, the following is **not** legal::

		rcu_read_lock();
		p = rcu_dereference(head.next);
		rcu_read_unlock();
		x = p->address;	/* BUG!!! */
		rcu_read_lock();
		y = p->data;	/* BUG!!! */
		rcu_read_unlock();

The Linux kernel CVE team has assigned CVE-2024-56654 to this issue.


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

	Issue introduced in 6.6 with commit a0bfde167b506423111ddb8cd71930497a40fc54 and fixed in 6.6.67 with commit 0108132d7d76d884e443d18b4f067cdf2811911b
	Issue introduced in 6.6 with commit a0bfde167b506423111ddb8cd71930497a40fc54 and fixed in 6.12.6 with commit f9ecc90b5d501b3a5a62d0685d5104f934bb0104
	Issue introduced in 6.6 with commit a0bfde167b506423111ddb8cd71930497a40fc54 and fixed in 6.13-rc3 with commit 581dd2dc168fe0ed2a7a5534a724f0d3751c93ae
	Issue introduced in 6.4.16 with commit b475c1109251e30ec21fb574d72a1c71a4ab0039
	Issue introduced in 6.5.3 with commit 2ccde10127447c1a5caad8469fede945bdb62fdf

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-56654
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/hci_event.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/0108132d7d76d884e443d18b4f067cdf2811911b
	https://git.kernel.org/stable/c/f9ecc90b5d501b3a5a62d0685d5104f934bb0104
	https://git.kernel.org/stable/c/581dd2dc168fe0ed2a7a5534a724f0d3751c93ae