From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] bluetooth 2026-03-19
Date: Thu, 19 Mar 2026 15:04:55 -0400 [thread overview]
Message-ID: <20260319190455.135302-1-luiz.dentz@gmail.com> (raw)
The following changes since commit 7ab4a7c5d969642782b8a5b608da0dd02aa9f229:
MPTCP: fix lock class name family in pm_nl_create_listen_socket (2026-03-19 09:37:48 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2026-03-19
for you to fetch changes up to 761fb8ec8778f0caf2bba5a41e3cff1ea86974f3:
Bluetooth: L2CAP: Fix regressions caused by reusing ident (2026-03-19 14:44:25 -0400)
----------------------------------------------------------------
bluetooth pull request for net:
- hci_ll: Fix firmware leak on error path
- hci_sync: annotate data-races around hdev->req_status
- L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb
- L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()
- L2CAP: Fix regressions caused by reusing ident
- L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req
- MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete
- SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
----------------------------------------------------------------
Anas Iqbal (1):
Bluetooth: hci_ll: Fix firmware leak on error path
Cen Zhang (1):
Bluetooth: hci_sync: annotate data-races around hdev->req_status
Helen Koike (1):
Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb
Hyunwoo Kim (2):
Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()
Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
Luiz Augusto von Dentz (2):
Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete
Bluetooth: L2CAP: Fix regressions caused by reusing ident
Minseo Park (1):
Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req
drivers/bluetooth/hci_ll.c | 2 ++
include/net/bluetooth/l2cap.h | 1 +
net/bluetooth/hci_conn.c | 2 +-
net/bluetooth/hci_core.c | 2 +-
net/bluetooth/hci_sync.c | 20 ++++++++++----------
net/bluetooth/l2cap_core.c | 40 ++++++++++++++++++++++++++++++++++------
net/bluetooth/l2cap_sock.c | 3 +++
net/bluetooth/mgmt.c | 2 +-
net/bluetooth/sco.c | 10 +++++++---
9 files changed, 60 insertions(+), 22 deletions(-)
next reply other threads:[~2026-03-19 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 19:04 Luiz Augusto von Dentz [this message]
2026-03-20 0:00 ` [GIT PULL] bluetooth 2026-03-19 patchwork-bot+netdevbpf
2026-03-20 16:47 ` bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19) Thorsten Leemhuis
2026-03-20 18:02 ` Luiz Augusto von Dentz
2026-03-20 18:26 ` bluetooth regression fix likely to miss -rc5 Thorsten Leemhuis
2026-03-20 21:03 ` bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19) Linus Torvalds
2026-03-20 21:19 ` Linus Torvalds
2026-03-21 18:50 ` Luiz Augusto von Dentz
2026-03-21 20:09 ` Linus Torvalds
2026-03-21 0:52 ` Jakub Kicinski
2026-03-21 18:36 ` Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260319190455.135302-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox