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: pull request: bluetooth 2024-05-03
Date: Fri, 3 May 2024 13:19:33 -0400 [thread overview]
Message-ID: <20240503171933.3851244-1-luiz.dentz@gmail.com> (raw)
The following changes since commit f2db7230f73a80dbb179deab78f88a7947f0ab7e:
tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). (2024-05-02 19:02:46 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2024-05-03
for you to fetch changes up to 40d442f969fb1e871da6fca73d3f8aef1f888558:
Bluetooth: qca: fix firmware check error path (2024-05-03 13:05:55 -0400)
----------------------------------------------------------------
bluetooth pull request for net:
- mediatek: mt8183-pico6: Fix bluetooth node
- sco: Fix use-after-free bugs caused by sco_sock_timeout
- l2cap: fix null-ptr-deref in l2cap_chan_timeout
- qca: Various fixes
- l2cap: Fix slab-use-after-free in l2cap_connect()
- msft: fix slab-use-after-free in msft_do_close()
- HCI: Fix potential null-ptr-deref
----------------------------------------------------------------
Chen-Yu Tsai (1):
arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node
Duoming Zhou (2):
Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout
Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
Johan Hovold (7):
Bluetooth: qca: fix wcn3991 device address check
Bluetooth: qca: add missing firmware sanity checks
Bluetooth: qca: fix NVM configuration parsing
Bluetooth: qca: generalise device address check
Bluetooth: qca: fix info leak when fetching fw build id
Bluetooth: qca: fix info leak when fetching board id
Bluetooth: qca: fix firmware check error path
Sungwoo Kim (3):
Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()
Bluetooth: msft: fix slab-use-after-free in msft_do_close()
Bluetooth: HCI: Fix potential null-ptr-deref
.../dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 +-
drivers/bluetooth/btqca.c | 110 +++++++++++++++++----
drivers/bluetooth/btqca.h | 3 +-
net/bluetooth/hci_core.c | 3 +-
net/bluetooth/hci_event.c | 2 +
net/bluetooth/l2cap_core.c | 24 ++---
net/bluetooth/msft.c | 2 +-
net/bluetooth/msft.h | 4 +-
net/bluetooth/sco.c | 4 +
9 files changed, 119 insertions(+), 36 deletions(-)
next reply other threads:[~2024-05-03 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 17:19 Luiz Augusto von Dentz [this message]
2024-05-03 22:40 ` pull request: bluetooth 2024-05-03 patchwork-bot+netdevbpf
2024-05-10 21:11 ` patchwork-bot+bluetooth
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=20240503171933.3851244-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).