Answer in brief
CVE-2024-26801 records a Unknown severity vulnerability in Bluetooth: Avoid potential use-after-free in hci_error_reset. 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.
Answer in brief
CVE-2024-26801 records a Unknown severity vulnerability in Bluetooth: Avoid potential use-after-free in hci_error_reset. 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 | >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <e0b278650f07acf2e0932149183458468a731c03 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <98fb98fd37e42fd4ce13ff657ea64503e24b6090 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <da4569d450b193e39e87119fd316c0291b585d14 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <45085686b9559bfbe3a4f41d3d695a520668f5e1 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2ab9a19d896f5a0dd386e1f001c5309bc35f433b || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <dd594cdc24f2e48dab441732e6dfcafd6b0711d1 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2449007d3f73b2842c9734f45f0aadb522daf592 | e0b278650f07acf2e0932149183458468a731c03, 98fb98fd37e42fd4ce13ff657ea64503e24b6090, 6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2, da4569d450b193e39e87119fd316c0291b585d14, 45085686b9559bfbe3a4f41d3d695a520668f5e1, 2ab9a19d896f5a0dd386e1f001c5309bc35f433b, dd594cdc24f2e48dab441732e6dfcafd6b0711d1, 2449007d3f73b2842c9734f45f0aadb522daf592 |
| Linux/Linuxgeneric | 4.0 | Not reported |
Published upstream
Apr 4, 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: Avoid potential use-after-free in hci_error_reset While handling the HCI_EV_HARDWARE_ERROR event, if the underlying BT controller is not responding, the GPIO reset mechanism would free the hci_dev and lead to a use-after-free in hci_error_reset. Here's the call trace observed on a ChromeOS device with Intel AX201: queue_work_on+0x3e/0x6c __hci_cmd_sync_sk+0x2ee/0x4c0 [bluetooth <HASH:3b4a6>] ? init_wait_entry+0x31/0x31 __hci_cmd_sync+0x16/0x20 [bluetooth <HASH:3b4a 6>] hci_error_reset+0x4f/0xa4 [bluetooth <HASH:3b4a 6>] process_one_work+0x1d8/0x33f worker_thread+0x21b/0x373 kthread+0x13a/0x152 ? pr_cont_work+0x54/0x54 ? kthread_blkcg+0x31/0x31 ret_from_fork+0x1f/0x30 This patch holds the reference count on the hci_dev while processing a HCI_EV_HARDWARE_ERROR event to avoid potential crash.
Quoted source text, attributed separately from HOL analysis.
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 | >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <e0b278650f07acf2e0932149183458468a731c03 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <98fb98fd37e42fd4ce13ff657ea64503e24b6090 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <da4569d450b193e39e87119fd316c0291b585d14 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <45085686b9559bfbe3a4f41d3d695a520668f5e1 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2ab9a19d896f5a0dd386e1f001c5309bc35f433b || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <dd594cdc24f2e48dab441732e6dfcafd6b0711d1 || >=c7741d16a57cbf97eebe53f27e8216b1ff20e20c <2449007d3f73b2842c9734f45f0aadb522daf592 | e0b278650f07acf2e0932149183458468a731c03, 98fb98fd37e42fd4ce13ff657ea64503e24b6090, 6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2, da4569d450b193e39e87119fd316c0291b585d14, 45085686b9559bfbe3a4f41d3d695a520668f5e1, 2ab9a19d896f5a0dd386e1f001c5309bc35f433b, dd594cdc24f2e48dab441732e6dfcafd6b0711d1, 2449007d3f73b2842c9734f45f0aadb522daf592 |
| Linux/Linuxgeneric | 4.0 | Not reported |
Published upstream
Apr 4, 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: Avoid potential use-after-free in hci_error_reset While handling the HCI_EV_HARDWARE_ERROR event, if the underlying BT controller is not responding, the GPIO reset mechanism would free the hci_dev and lead to a use-after-free in hci_error_reset. Here's the call trace observed on a ChromeOS device with Intel AX201: queue_work_on+0x3e/0x6c __hci_cmd_sync_sk+0x2ee/0x4c0 [bluetooth <HASH:3b4a6>] ? init_wait_entry+0x31/0x31 __hci_cmd_sync+0x16/0x20 [bluetooth <HASH:3b4a 6>] hci_error_reset+0x4f/0xa4 [bluetooth <HASH:3b4a 6>] process_one_work+0x1d8/0x33f worker_thread+0x21b/0x373 kthread+0x13a/0x152 ? pr_cont_work+0x54/0x54 ? kthread_blkcg+0x31/0x31 ret_from_fork+0x1f/0x30 This patch holds the reference count on the hci_dev while processing a HCI_EV_HARDWARE_ERROR event to avoid potential crash.
Quoted source text, attributed separately from HOL analysis.