### [CVE-2024-26801](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26801)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=4.0%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=c7741d16a57cbf97eebe53f27e8216b1ff20e20c%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:Bluetooth: Avoid potential use-after-free in hci_error_resetWhile handling the HCI_EV_HARDWARE_ERROR event, if the underlyingBT controller is not responding, the GPIO reset mechanism wouldfree 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/0x30This patch holds the reference count on the hci_dev while processinga HCI_EV_HARDWARE_ERROR event to avoid potential crash.

### POC

#### Reference
- https://git.kernel.org/stable/c/98fb98fd37e42fd4ce13ff657ea64503e24b6090

#### Github
No PoCs found on GitHub currently.