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-31771Bluetooth: hci_event: move wake reason storage into validated event handlers

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: move wake reason storage into validated event handlers hci_store_wake_reason() is called from hci_event_packet() immediately after stripping the HCI event header but before hci_event_func() enforces the per-event minimum payload length from hci_ev_table. This means a short HCI event frame can reach bacpy() before any bounds check runs. Rather than duplicating skb parsing and per-event length checks inside hci_store_wake_reason(), move wake-address storage into the individual event handlers after their existing event-length validation has succeeded. Convert hci_store_wake_reason() into a small helper that only stores an already-validated bdaddr while the caller holds hci_dev_lock(). Use the same helper after hci_event_func() with a NULL address to preserve the existing unexpected-wake fallback semantics when no validated event handler records a wake address. Annotate the helper with __must_hold(&hdev->lock) and add lockdep_assert_held(&hdev->lock) so future call paths keep the lock contract explicit. Call the helper from hci_conn_request_evt(), hci_conn_complete_evt(), hci_sync_conn_complete_evt(), le_conn_complete_evt(), hci_le_adv_report_evt(), hci_le_ext_adv_report_evt(), hci_le_direct_adv_report_evt(), hci_le_pa_sync_established_evt(), and hci_le_past_received_evt().

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-31771, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Modified3.1High8.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < fbea63d0d301edd4a42f4390b49b8519d78b802d
    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < 1e4b738dd0d0f7b237686167706badad9d30649c
    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < ac7889b0fe441e4ef892c40b1d002e91f93fa4ae
    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < dbc8b8d33c9e19e17e8b8b1361bbb46e2983f5f2
    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < 86c8d07a64d553c41e213b52650020010f9ef23e
    • affected 2f20216c1d6fe17c1a224f658be0dc6fab2269c7 – < 2b2bf47cd75518c36fa2d41380e4a40641cc89cd
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .