Bluetooth: hci_sock: reject out-of-range OCF values
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 173457fa3e99ef4188dd0fe63e4dee98d0e441a9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sock: reject out-of-range OCF values
The raw HCI socket security filter has 128 OCF bits per supported OGF, but masks the 10-bit OCF with 127 before looking up the command. An unprivileged socket can therefore submit a reserved OCF that aliases an allowlisted command modulo 128.
A conforming controller should reject reserved opcodes. Nevertheless, the security decision must apply to the opcode that will actually be sent, especially since controller-specific behavior is outside the host stack's control.
Reject OCF values that cannot be represented by the security filter instead of aliasing them onto an unrelated command.
From the CVE record · Linux
The Bluetooth raw HCI socket security filter can treat an out-of-range command value as an allowlisted command. A local, unprivileged attacker with a raw HCI socket can submit a reserved opcode that passes the filter; a conforming controller should reject it.
Engineers running Linux kernels with the affected Bluetooth hci_sock code should check their kernel version; affected versions were not specified.