CVE-2026-31773High· 8.8▾ TwilightIn 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 w…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
Last analysed / modified upstream
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.
Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 9a38659a3d06080715691bd3139f9c4b61f688e3Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 667f44f1392df6482483756458c48670e579e9ffLinux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 929db734d12db41ca5f95424db4612397f1bd4a7Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < b1c6a8e554a39b222c0879a288ea98e338fc4d77Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 0afc846bd80073ffcd2b8040f2b2fafaea3d9f72Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 061ee71ac6b03c9f8432fe49538c3682bfcf4cf3Linux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 9a6d0db176f082685e0b6149700c0baf3ce2aa8bLinux >= fff3490f47810e2d34b91fb9e31103e923b11c2f < 20756fec2f0108cb88e815941f1ffff88dc286feLinux 14ec593d6bb050cf40a4ade2f9ac9ca050e0412cLinux >= 3.15.5 < 3.16Linux 3.16Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets