Bluetooth: hci_event: move wake reason storage into validated event handlers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.19.12, Kernel 2b2bf47cd75518c36fa2d41380e4a40641cc89cd, Kernel 86c8d07a64d553c41e213b52650020010f9ef23e and 8 more.
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().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.10 <6.19.12, =7.0, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <2b2bf47cd75518c36fa2d41380e4a40641cc89cd, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <86c8d07a64d553c41e213b52650020010f9ef23e, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <ac7889b0fe441e4ef892c40b1d002e91f93fa4ae, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <dbc8b8d33c9e19e17e8b8b1361bbb46e2983f5f2, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <fbea63d0d301edd4a42f4390b49b8519d78b802d, =5.10, >=2f20216c1d6fe17c1a224f658be0dc6fab2269c7 <1e4b738dd0d0f7b237686167706badad9d30649c | 6.19.12, 2b2bf47cd75518c36fa2d41380e4a40641cc89cd, 86c8d07a64d553c41e213b52650020010f9ef23e, ac7889b0fe441e4ef892c40b1d002e91f93fa4ae, dbc8b8d33c9e19e17e8b8b1361bbb46e2983f5f2, fbea63d0d301edd4a42f4390b49b8519d78b802d, 1e4b738dd0d0f7b237686167706badad9d30649c |
| linux-kernel: Kernel | >=5.10.0 <6.1.191, >=6.13.0 <6.18.57, >=6.19.0 <6.19.12, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114 | 6.1.191, 6.18.57, 6.19.12, 6.6.160, 6.12.114 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket