Bluetooth: SMP: force responder MITM requirements before building the pairing response
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in 425a22c5373d4e1b46492ab869074ebeeade61f3; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in 7ab69426e7ecbd18a222ee2ec87ca612d30197d7; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in 01bb4045d2306c266178f49ce0c3576d237a3040; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in 91649c02c1baaa18cedf7fb425fa1f0f852c8183; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in fa14e0e19820b1bbdb42185c9c4efa950bcffef9; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in ec17efb1ef91506cfd17a77692eaf4bbacb520ea; From 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 · fixed in d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7
- Linux Linux
3.3
- KernelLinux
From 3.3.0 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.168; From 6.2.0 · fixed in 6.6.134; From 6.7.0 · fixed in 6.12.81; From 6.13.0 · fixed in 6.18.22; From 6.19.0 · fixed in 6.19.12
References 8
git.kernel.org
- stable/c/425a22c5373d4e1b46492ab869074ebeeade61f3
- stable/c/7ab69426e7ecbd18a222ee2ec87ca612d30197d7
- stable/c/01bb4045d2306c266178f49ce0c3576d237a3040
- stable/c/91649c02c1baaa18cedf7fb425fa1f0f852c8183
- stable/c/c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb
- stable/c/fa14e0e19820b1bbdb42185c9c4efa950bcffef9
- stable/c/ec17efb1ef91506cfd17a77692eaf4bbacb520ea
- stable/c/d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7