CVE-2026-31771

High

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().

SeverityHigh
CVSS8.1
Exploit probability—
ProductLinux Kernel
PublishedMay 1, 2026
First seenMay 1, 2026

How to fix

Update
  • linux linux_kernel6.19.12 or later

Affected products

ProductAffected versionsFixed in
linux linux_kernel5.10 ≤ v < 6.19.12, 7.06.19.12
microsoft azl3_kernel_6.6.137.1-2No range specified—
microsoft azl3_kernel_6.6.138.1-1No range specified—
microsoft azl3_kernel_6.6.145.2-1No range specified—
microsoft azl3_kernel_6.6.152.1-1No range specified—
microsoft azl3_kernel_6.6.134.1-2No range specified—
microsoft azl3_kernel_6.6.139.1-1No range specified—
microsoft azl3_kernel_6.6.141.1-1No range specified—
microsoft azl3_kernel_6.6.143.1-1No range specified—
microsoft azl3_kernel_6.6.144.1-1No range specified—
microsoft azl3_kernel_6.6.150.1-1No range specified—
microsoft azl3_kernel_6.6.157.1-1No range specified—
microsoft azl3_kernel_6.6.159.1-1No range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.