CVE-2024-56654
MediumIn 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();
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
6.4.16,
6.5.3,
6.6
and later are affected. Fixed in
6.6.67,
6.12.6,
6.13
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2024-56654?
CVE-2024-56654 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.4.16 onward and has been patched in 6.6.67, 6.12.6 and 6.13. CVE-2024-56654 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2024-56654?
CVE-2024-56654 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2024-56654?
Yes. CVE-2024-56654 has been patched. Fixed versions include 6.6.67, 6.12.6 and 6.13. If you are running Linux kernel 6.4.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2024-56654 actively exploited?
No. CVE-2024-56654 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.