Re: [PATCH 6.1] Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync

[Sasha Levin <sashal@kernel.org>]

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 5af1f84ed13a416297ab9ced7537f4d5ae7f329a

WARNING: Author mismatch between patch and upstream commit:
Backport author: Sumanth Gavini <sumanth.gavini@yahoo.com>
Commit author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  5af1f84ed13a ! 1:  347ef4c82277 Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync
    @@
      ## Metadata ##
    -Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    +Author: Sumanth Gavini <sumanth.gavini@yahoo.com>
     
      ## Commit message ##
         Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync
     
    +    commit 5af1f84ed13a416297ab9ced7537f4d5ae7f329a upstream.
    +
         Connections may be cleanup while waiting for the commands to complete so
         this attempts to check if the connection handle remains valid in case of
         errors that would lead to call hci_conn_failed:
    @@ Commit message
          hci_abort_conn_sync+0x237/0x360
     
         Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    +    Signed-off-by: Sumanth Gavini <sumanth.gavini@yahoo.com>
     
      ## net/bluetooth/hci_sync.c ##
     @@ net/bluetooth/hci_sync.c: static int hci_reject_conn_sync(struct hci_dev *hdev, struct hci_conn *conn,
    @@ net/bluetooth/hci_sync.c: static int hci_reject_conn_sync(struct hci_dev *hdev,
     +		err = hci_disconnect_sync(hdev, conn, reason);
     +		break;
      	case BT_CONNECT:
    - 		err = hci_connect_cancel_sync(hdev, conn, reason);
    + 		err = hci_connect_cancel_sync(hdev, conn);
     -		/* Cleanup hci_conn object if it cannot be cancelled as it
    --		 * likelly means the controller and host stack are out of sync
    --		 * or in case of LE it was still scanning so it can be cleanup
    --		 * safely.
    +-		 * likelly means the controller and host stack are out of sync.
     -		 */
     -		if (err) {
     -			hci_dev_lock(hdev);
    @@ net/bluetooth/hci_sync.c: static int hci_reject_conn_sync(struct hci_dev *hdev,
     -		return hci_reject_conn_sync(hdev, conn, reason);
     +		err = hci_reject_conn_sync(hdev, conn, reason);
     +		break;
    - 	case BT_OPEN:
    - 	case BT_BOUND:
    - 		hci_dev_lock(hdev);
    -@@ net/bluetooth/hci_sync.c: int hci_abort_conn_sync(struct hci_dev *hdev, struct hci_conn *conn, u8 reason)
    - 		return 0;
      	default:
      		conn->state = BT_CLOSED;
     -		break;

---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.1.y        | Success     | Success    |