Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.4.76.5In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link
hci_connect_sco currently returns NULL when there is no link (i.e. when hci_conn_link() returns NULL).
sco_connect() expects an ERR_PTR in case of any error (see line 266 in sco.c). Thus, hcon set as NULL passes through to sco_conn_add(), which tries to get hcon->hdev, resulting in dereferencing a NULL pointer as reported by syzkaller.
The same issue exists for iso_connect_cis() calling hci_connect_cis().
Thus, make hci_connect_sco() and hci_connect_cis() return ERR_PTR instead of NULL.
From the CVE record · Linux
The Linux kernel Bluetooth connection code can return NULL when no link exists, while its callers expect an error pointer. This can lead to a NULL pointer dereference. The input does not establish whether triggering it requires local or network access, authentication, or user interaction.
Anyone running the Linux kernel should check whether their version includes the Bluetooth hci_conn fix; affected versions are not specified.