Executive Summary

Informations
Name CVE-2024-56654 First vendor Publication 2024-12-27
Vendor Cve Last vendor Modification 2025-01-06

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
Exploitabality Sub Score 1.8
 
Attack Vector Local Attack Complexity Low
Privileges Required Low User Interaction None
Scope Unchanged Confidentiality Impact None
Integrity Impact None Availability Impact High
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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();

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56654

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3703

Sources (Detail)

https://git.kernel.org/stable/c/0108132d7d76d884e443d18b4f067cdf2811911b
https://git.kernel.org/stable/c/581dd2dc168fe0ed2a7a5534a724f0d3751c93ae
https://git.kernel.org/stable/c/f9ecc90b5d501b3a5a62d0685d5104f934bb0104
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Date Informations
2025-07-15 02:41:13
  • Multiple Updates
2025-07-14 12:38:30
  • Multiple Updates
2025-06-26 02:38:28
  • Multiple Updates
2025-06-25 12:36:31
  • Multiple Updates
2025-06-24 02:43:05
  • Multiple Updates
2025-05-27 02:48:31
  • Multiple Updates
2025-03-29 03:44:24
  • Multiple Updates
2025-03-28 13:47:40
  • Multiple Updates
2025-03-28 03:22:13
  • Multiple Updates
2025-03-19 03:17:02
  • Multiple Updates
2025-03-18 03:30:02
  • Multiple Updates
2025-03-14 03:17:09
  • Multiple Updates
2025-03-06 14:13:42
  • Multiple Updates
2025-02-22 03:27:14
  • Multiple Updates
2025-01-08 00:20:56
  • Multiple Updates
2025-01-07 03:08:11
  • Multiple Updates
2025-01-07 00:20:44
  • Multiple Updates
2024-12-27 21:20:28
  • First insertion