CVE-2026-31773
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: derive legacy responder STK authentication from MITM state
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: derive legacy responder STK authentication from MITM state The legacy responder path in smp_random() currently labels the stored STK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH. That reflects what the local service requested, not what the pairing flow actually achieved. For Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear and the resulting STK should remain unauthenticated even if the local side requested HIGH security. Use the established MITM state when storing the responder STK so the key metadata matches the pairing result. This also keeps the legacy path aligned with the Secure Connections code, which already treats JUST_WORKS/JUST_CFM as unauthenticated.
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) |
|---|---|---|---|---|---|
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 9a38659a3d06080715691bd3139f9c4b61f688e3 | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 667f44f1392df6482483756458c48670e579e9ff | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 929db734d12db41ca5f95424db4612397f1bd4a7 | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | b1c6a8e554a39b222c0879a288ea98e338fc4d77 | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 0afc846bd80073ffcd2b8040f2b2fafaea3d9f72 | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 061ee71ac6b03c9f8432fe49538c3682bfcf4cf3 | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 9a6d0db176f082685e0b6149700c0baf3ce2aa8b | Unavailable | None listed |
| fff3490f47810e2d34b91fb9e31103e923b11c2f | affected | git | 20756fec2f0108cb88e815941f1ffff88dc286fe | Unavailable | None listed |
| 14ec593d6bb050cf40a4ade2f9ac9ca050e0412c | affected | git | Unavailable | Unavailable | None listed |
| 3.15.5 | affected | semver | 3.16 | 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.16 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 3.16 | 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 |