Bug 2334563 (CVE-2024-56654) - CVE-2024-56654 kernel: Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating
Summary: CVE-2024-56654 kernel: Bluetooth: hci_event: Fix using rcu_read_(un)lock whil...
Keywords:
Status: NEW
Alias: CVE-2024-56654
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-27 16:03 UTC by OSIDB Bzimport
Modified: 2025-05-13 08:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:6966 0 None None None 2025-05-13 08:37:54 UTC

Description OSIDB Bzimport 2024-12-27 16:03:48 UTC
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();

Comment 1 Avinash Hanwate 2024-12-28 01:49:40 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56654-66a1@gregkh/T

Comment 2 errata-xmlrpc 2025-05-13 08:37:53 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:6966 https://access.redhat.com/errata/RHSA-2025:6966


Note You need to log in before you can comment on or make changes to this bug.