IT

Tracker / CVE-2026-31773

CVE-2026-31773

High 8.8

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.

Affected products and versions

linux linux_kernel
linux linux_kernel · 3.15.5 → 3.16
linux linux_kernel · 3.16.1 → 5.10.253
linux linux_kernel · 5.11 → 5.15.203
linux linux_kernel · 5.16 → 6.1.168
linux linux_kernel · 6.13 → 6.18.22
linux linux_kernel · 6.19 → 6.19.12
linux linux_kernel · 6.2 → 6.6.134
linux linux_kernel · 6.7 → 6.12.81

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References