CVE-2026-43334
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
Bluetooth: SMP: force responder MITM requirements before building the pairing response
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | 425a22c5373d4e1b46492ab869074ebeeade61f3 | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | 7ab69426e7ecbd18a222ee2ec87ca612d30197d7 | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | 01bb4045d2306c266178f49ce0c3576d237a3040 | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | 91649c02c1baaa18cedf7fb425fa1f0f852c8183 | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | fa14e0e19820b1bbdb42185c9c4efa950bcffef9 | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | ec17efb1ef91506cfd17a77692eaf4bbacb520ea | Unavailable | None listed |
| 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 | affected | git | d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 3.3 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 3.3 | Unavailable | None listed |
| 5.10.253 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.203 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.1.168 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.134 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.81 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.22 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 6.19.12 | unaffected | semver | Unavailable | 6.19.* | None listed |
| 7.0 | unaffected | original_commit_for_fix | Unavailable | * | None listed |