Re: [PATCH v3] Bluetooth: hci_event: move wake reason storage into validated event handlers

["gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>]

On Thu, Mar 26, 2026 at 01:32:50PM +0000, Oleh Konko wrote:
> From f0e8b2abaf4a895fad81756277014582c773808d Mon Sep 17 00:00:00 2001
> From: Oleh Konko <security@1seal.org>
> Date: Thu, 26 Mar 2026 14:29:58 +0100
> Subject: [PATCH v3] Bluetooth: hci_event: move wake reason storage into
>  validated event handlers

If you use git send-email, the header will not be in the body like this.

> 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.
> 
> Call the helper from hci_conn_request_evt(), hci_conn_complete_evt(),
> hci_le_adv_report_evt(), hci_le_ext_adv_report_evt(), and
> hci_le_direct_adv_report_evt().
> 
> Fixes: 2f20216c1d6f ("Bluetooth: Emit controller suspend and resume events")
> Cc: stable@vger.kernel.org
> Signed-off-by: Oleh Konko <security@1seal.org>
> ---
> v3:
> - route the unexpected-wake fallback through hci_store_wake_reason(NULL, 0)
>   after hci_event_func(), as suggested in review
> 
>  net/bluetooth/hci_event.c | 89 +++++++++++++--------------------------
>  1 file changed, 29 insertions(+), 60 deletions(-)
> 
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 286529d2e..c0e0b4a1c 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -80,6 +80,9 @@ static void *hci_le_ev_skb_pull(struct hci_dev *hdev, struct sk_buff *skb,
>  	return data;
>  }
>  
> +static void hci_store_wake_reason(struct hci_dev *hdev,
> +				  const bdaddr_t *bdaddr, u8 addr_type);
> +
>  static u8 hci_cc_inquiry_cancel(struct hci_dev *hdev, void *data,
>  				struct sk_buff *skb)
>  {
> @@ -3111,6 +3114,7 @@ static void hci_conn_complete_evt(struct hci_dev *hdev, void *data,
>  	bt_dev_dbg(hdev, "status 0x%2.2x", status);
>  
>  	hci_dev_lock(hdev);
> +	hci_store_wake_reason(hdev, &ev->bdaddr, BDADDR_BREDR);
>  
>  	/* Check for existing connection:
>  	 *
> @@ -3274,6 +3278,10 @@ static void hci_conn_request_evt(struct hci_dev *hdev, void *data,
>  
>  	bt_dev_dbg(hdev, "bdaddr %pMR type 0x%x", &ev->bdaddr, ev->link_type);
>  
> +	hci_dev_lock(hdev);
> +	hci_store_wake_reason(hdev, &ev->bdaddr, BDADDR_BREDR);
> +	hci_dev_unlock(hdev);
> +
>  	/* Reject incoming connection from device with same BD ADDR against
>  	 * CVE-2020-26555
>  	 */
> @@ -6403,6 +6411,8 @@ static void hci_le_adv_report_evt(struct hci_dev *hdev, void *data,
>  					info->length + 1))
>  			break;
>  
> +		hci_store_wake_reason(hdev, &info->bdaddr, info->bdaddr_type);
> +
>  		if (info->length <= max_adv_len(hdev)) {
>  			rssi = info->data[info->length];
>  			process_adv_report(hdev, info->type, &info->bdaddr,
> @@ -6491,6 +6501,8 @@ static void hci_le_ext_adv_report_evt(struct hci_dev *hdev, void *data,
>  					info->length))
>  			break;
>  
> +		hci_store_wake_reason(hdev, &info->bdaddr, info->bdaddr_type);
> +
>  		evt_type = __le16_to_cpu(info->type) & LE_EXT_ADV_EVT_TYPE_MASK;
>  		legacy_evt_type = ext_evt_type_to_legacy(hdev, evt_type);
>  
> @@ -6834,6 +6846,8 @@ static void hci_le_direct_adv_report_evt(struct hci_dev *hdev, void *data,
>  	for (i = 0; i < ev->num; i++) {
>  		struct hci_ev_le_direct_adv_info *info = &ev->info[i];
>  
> +		hci_store_wake_reason(hdev, &info->bdaddr, info->bdaddr_type);
> +
>  		process_adv_report(hdev, info->type, &info->bdaddr,
>  				   info->bdaddr_type, &info->direct_addr,
>  				   info->direct_addr_type, HCI_ADV_PHY_1M, 0,
> @@ -7517,73 +7531,27 @@ static bool hci_get_cmd_complete(struct hci_dev *hdev, u16 opcode,
>  	return true;
>  }
>  
> -static void hci_store_wake_reason(struct hci_dev *hdev, u8 event,
> -				  struct sk_buff *skb)
> +/* hdev lock must be held. pass NULL bdaddr to record an unexpected wake. */
> +static void hci_store_wake_reason(struct hci_dev *hdev,
> +				  const bdaddr_t *bdaddr, u8 addr_type)

If the lock must be held, why aren't you both adding the static test for
this at build time __must_hold(), and the runtime lock test so that we
know this lock is held?  That way any changes in any code paths in the
future will properly trigger at build and runtime to know to be fixed
up.

thanks,

greg k-h