CVE-2024-56654: Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating
First published: Fri Dec 27 2024(Updated: )
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();
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.4.16<6.5 | |
| Linux Kernel | >=6.5.3<6.6.67 | |
| Linux Kernel | >=6.7<6.12.6 | |
| Linux Kernel | =6.13-rc1 | |
| Linux Kernel | =6.13-rc2 | |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/0108132d7d76d884e443d18b4f067cdf2811911b
- https://git.kernel.org/stable/c/f9ecc90b5d501b3a5a62d0685d5104f934bb0104
- https://git.kernel.org/stable/c/581dd2dc168fe0ed2a7a5534a724f0d3751c93ae
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56654
- https://nvd.nist.gov/vuln/detail/CVE-2024-56654
- https://launchpad.net/bugs/cve/CVE-2024-56654
- https://security-tracker.debian.org/tracker/CVE-2024-56654
- https://ubuntu.com/security/CVE-2024-56654
- https://git.kernel.org/linus/581dd2dc168fe0ed2a7a5534a724f0d3751c93ae
Frequently Asked Questions
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.
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.
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.
Is there a workaround for CVE-2024-56654?
There are no known workarounds for CVE-2024-56654; updating the kernel is the recommended approach.
What components of the Linux kernel are impacted by CVE-2024-56654?
CVE-2024-56654 specifically impacts the Bluetooth subsystem of the Linux kernel.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- collector/nvd-cve
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.4.16
- version/linux kernel/6.5.3
- version/linux kernel/6.7
- version/linux kernel/6.13-rc1
- version/linux kernel/6.13-rc2
- package-manager/debian