Bluetooth: SMP: force responder MITM requirements before building the pairing response
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.253, Kernel 5.15.203, Kernel 6.1.168 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: force responder MITM requirements before building the pairing response smp_cmd_pairing_req() currently builds the pairing response from the initiator auth_req before enforcing the local BT_SECURITY_HIGH requirement. If the initiator omits SMP_AUTH_MITM, the response can also omit it even though the local side still requires MITM. tk_request() then sees an auth value without SMP_AUTH_MITM and may select JUST_CFM, making method selection inconsistent with the pairing policy the responder already enforces. When the local side requires HIGH security, first verify that MITM can be achieved from the IO capabilities and then force SMP_AUTH_MITM in the response in both rsp.auth_req and auth. This keeps the responder auth bits and later method selection aligned.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3.3 <5.10.253, >=5.11 <5.15.203, >=5.16 <6.1.168, >=6.13 <6.18.22, >=6.19 <6.19.12, >=6.2 <6.6.134, >=6.7 <6.12.81, =7.0, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <425a22c5373d4e1b46492ab869074ebeeade61f3, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <7ab69426e7ecbd18a222ee2ec87ca612d30197d7, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <91649c02c1baaa18cedf7fb425fa1f0f852c8183, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <ec17efb1ef91506cfd17a77692eaf4bbacb520ea, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <fa14e0e19820b1bbdb42185c9c4efa950bcffef9, =3.3, >=2b64d153a0cc9d2b60e47be013cde8490f16e0a5 <01bb4045d2306c266178f49ce0c3576d237a3040 | 5.10.253, 5.15.203, 6.1.168, 6.18.22, 6.19.12, 6.6.134, 6.12.81, 425a22c5373d4e1b46492ab869074ebeeade61f3, 7ab69426e7ecbd18a222ee2ec87ca612d30197d7, 91649c02c1baaa18cedf7fb425fa1f0f852c8183, c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb, d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7, ec17efb1ef91506cfd17a77692eaf4bbacb520ea, fa14e0e19820b1bbdb42185c9c4efa950bcffef9, 01bb4045d2306c266178f49ce0c3576d237a3040 |
| linux-kernel: Kernel | >=3.3.0 <5.10.253, >=5.11.0 <5.15.203, >=5.16.0 <6.1.168, >=6.13.0 <6.18.22, >=6.19.0 <6.19.12, >=6.2.0 <6.6.134, >=6.7.0 <6.12.81 | 5.10.253, 5.15.203, 6.1.168, 6.18.22, 6.19.12, 6.6.134, 6.12.81 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket