CVE-2026-64433

Schwachstellenklasse

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete add_device_complete() runs from the hci_cmd_sync_work kworker, which holds only hci_req_sync_lock and *not* hci_dev_lock. It calls hci_conn_params_lookup() and then dereferences the returned object (params->flags) without taking hci_dev_lock: params = hci_conn_params_lookup(hdev, &cp->addr.bdaddr, le_addr_type(cp->addr.type)); ... device_flags_changed(NULL, hdev, &cp->addr.bdaddr, cp->addr.type, hdev->conn_flags, params ? params->flags : 0); hci_conn_params_lookup() walks hdev->le_conn_params and is documented to require hdev->lock. A concurrent MGMT_OP_REMOVE_DEVICE (remove_device()), which does run under hci_dev_lock, can call hci_conn_params_free() to list_del() and kfree() the very object the lookup returned, so the subsequent params->flags read touches freed memory [0]. Hold hci_dev_lock() across the hci_conn_params_lookup() and the read of params->flags (and the matching event emission) so the lookup result cannot be freed by a concurrent remove_device() before it is used, honouring the locking contract of hci_conn_params_lookup(). [0]: (trail

Betroffene Produkte

• linux linux_kernel

Quellen

• https://git.kernel.org/stable/c/9531014c60c804e16099885d4a98aedcf31bce8d
• https://git.kernel.org/stable/c/b346efa825b5e4386f19bc63f81141652d496ec4
• https://git.kernel.org/stable/c/caed4a96d55757c139a899744657c032b6186665
• https://git.kernel.org/stable/c/e4369e4e970f3fa4676b76be14c1d315c87f22b6
• https://git.kernel.org/stable/c/fa85d985f614bc3feb343000f14a1072e99b0df1