Bluetooth: Fix OOB data present value for SMP pairing
Subsystems (2)
Marcel Holtmann
maintainerPATCH 1/1 Bluetooth: Fix OOB data present value for SMP pairing
Before setting the OOB data present flag with SMP pairing, check the newly introduced present tracking that actual OOB data values have been provided. The existence of remote OOB data structure does not actually mean that the correct data values are available.
Signed-off-by Marcel Holtmann <[email protected]>
--- net/bluetooth/smp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/bluetooth/smp.c +1 -1
@@ -620,7 +620,7 @@ static void build_pairing_cmd(struct l2cap_conn *conn, oob_data =hci_find_remote_oob_data (hdev, &hcon->dst, bdaddr_type); -if (oob_data) { +if (oob_data && oob_data->present) {set_bit (SMP_FLAG_OOB , &smp->flags); oob_flag =SMP_OOB_PRESENT ;memcpy (smp->rr, oob_data->rand256,16 );
Signature · 1 line
2.1.0
Johan Hedberg
AppliedHi Marcel,
Quoted 9 lines · Marcel Holtmann
Before setting the OOB data present flag with SMP pairing, check the newly introduced present tracking that actual OOB data values have been provided. The existence of remote OOB data structure does not actually mean that the correct data values are available.
Signed-off-by Marcel Holtmann <[email protected]>--- net/bluetooth/smp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to bluetooth-next. Thanks.
Johan