Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7b445e220db9a2c58be5d09bbbd322abf1b1452a · < da55f570191d5d72f10c607a7043b947eb05ea46| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds
Dereferencing RCU-protected pointers outside critical sections is invalid and may lead to UAF. Use of hci_conn in hci_sync callbacks also needs to hold refcount to avoid UAF.
Take appropriate locks for hci_conn lookups, and take refcount for hci_conn pointers stored in mgmt_pending_cmd so that the pointer stays valid.
When accessing conn->state, ensure hdev->lock is held to avoid data race.
From the CVE record · Linux
The Linux kernel’s Bluetooth management code can use an hci_conn pointer after it has been freed because some accesses lack the required lock or reference. The input does not specify how an attacker could trigger this issue, whether authentication or user interaction is needed, or what an attacker could achieve.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.