Answer in brief
CVE-2024-56654 records a Unknown severity vulnerability in Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a0bfde167b506423111ddb8cd71930497a40fc54 <0108132d7d76d884e443d18b4f067cdf2811911b || >=a0bfde167b506423111ddb8cd71930497a40fc54 <f9ecc90b5d501b3a5a62d0685d5104f934bb0104 || >=a0bfde167b506423111ddb8cd71930497a40fc54 <581dd2dc168fe0ed2a7a5534a724f0d3751c93ae || b475c1109251e30ec21fb574d72a1c71a4ab0039 || 2ccde10127447c1a5caad8469fede945bdb62fdf || >=6.4.16 <6.5 || >=6.5.3 <6.6 | 0108132d7d76d884e443d18b4f067cdf2811911b, f9ecc90b5d501b3a5a62d0685d5104f934bb0104, 581dd2dc168fe0ed2a7a5534a724f0d3751c93ae, 6.5, 6.6 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Dec 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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();
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-56654 records a Unknown severity vulnerability in Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a0bfde167b506423111ddb8cd71930497a40fc54 <0108132d7d76d884e443d18b4f067cdf2811911b || >=a0bfde167b506423111ddb8cd71930497a40fc54 <f9ecc90b5d501b3a5a62d0685d5104f934bb0104 || >=a0bfde167b506423111ddb8cd71930497a40fc54 <581dd2dc168fe0ed2a7a5534a724f0d3751c93ae || b475c1109251e30ec21fb574d72a1c71a4ab0039 || 2ccde10127447c1a5caad8469fede945bdb62fdf || >=6.4.16 <6.5 || >=6.5.3 <6.6 | 0108132d7d76d884e443d18b4f067cdf2811911b, f9ecc90b5d501b3a5a62d0685d5104f934bb0104, 581dd2dc168fe0ed2a7a5534a724f0d3751c93ae, 6.5, 6.6 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Dec 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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();
Quoted source text, attributed separately from HOL analysis.