CVE-2024-56654: Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating

Published Dec 27, 2024
·
Updated

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

Bluetooth: hcievent: Fix using rcuread(un)lock while iterating

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

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

rcureadlock(); p = rcudereference(head.next); rcureadunlock(); x = p->address; / BUG!!! / rcureadlock(); y = p->data; / BUG!!! / rcureadunlock();

Other sources

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

Bluetooth: hcievent: Fix using rcuread(un)lock while iterating

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

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

rcureadlock(); p = rcudereference(head.next); rcureadunlock(); x = p->address; / BUG!!! / rcureadlock(); y = p->data; / BUG!!! / rcureadunlock();

NVD

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

6 affected componentsFixes available
Linux Linux kernel>=6.4.16<6.5
Linux Linux kernel>=6.5.3<6.6.67
Linux Linux kernel>=6.7<6.12.6
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1

Event History

Dec 27, 2024
CVE Published
via MITRE·03:06 PM
Data Sourced
via MITRE·03:06 PM
DescriptionSeverity
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Red Hat·04:03 PM
DescriptionSeverityAffected Software
Mar 27, 2025
Data Sourced
via Launchpad·06:46 PM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·06:53 PM
RemedyDescriptionSeverityAffected Software
Jan 12, 58561
Event
via MITRE·12:53 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-56654?

The severity of CVE-2024-56654 has not been publicly assigned but it affects the Linux kernel Bluetooth implementation.

2

How do I fix CVE-2024-56654?

To fix CVE-2024-56654, update your Linux kernel to a version that includes the patch for this vulnerability.

3

What versions of the Linux kernel are affected by CVE-2024-56654?

CVE-2024-56654 affects Linux kernel versions from 6.4.16 to 6.5, as well as several versions in the 6.5.x and 6.6.x series.

4

Is there a workaround for CVE-2024-56654?

There are no known workarounds for CVE-2024-56654; updating the kernel is the recommended approach.

5

What components of the Linux kernel are impacted by CVE-2024-56654?

CVE-2024-56654 specifically impacts the Bluetooth subsystem of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203