Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31773Bluetooth: SMP: derive legacy responder STK authentication from MITM state

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31773, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 9a38659a3d06080715691bd3139f9c4b61f688e3
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 667f44f1392df6482483756458c48670e579e9ff
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 929db734d12db41ca5f95424db4612397f1bd4a7
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < b1c6a8e554a39b222c0879a288ea98e338fc4d77
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 0afc846bd80073ffcd2b8040f2b2fafaea3d9f72
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 061ee71ac6b03c9f8432fe49538c3682bfcf4cf3
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 9a6d0db176f082685e0b6149700c0baf3ce2aa8b
    • affected fff3490f47810e2d34b91fb9e31103e923b11c2f – < 20756fec2f0108cb88e815941f1ffff88dc286fe
    • affected 14ec593d6bb050cf40a4ade2f9ac9ca050e0412c
    • affected 3.15.5 – < 3.16
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31773 badge
[![CVE-2026-31773](https://cveledger.app/badge/CVE-2026-31773.svg)](https://cveledger.app/cve/CVE-2026-31773)

Record last updated .