To: Ruihan Li <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org,
Subject: Re: [PATCH] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
Date: Mon, 17 Apr 2023 18:30:19 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <firstname.lastname@example.org>:
On Sun, 16 Apr 2023 16:02:51 +0800 you wrote:
> Previously, channel open messages were always sent to monitors on the first
> ioctl() call for unbound HCI sockets, even if the command and arguments
> were completely invalid. This can leave an exploitable hole with the abuse
> of invalid ioctl calls.
> This commit hardens the ioctl processing logic by first checking if the
> command is valid, and immediately returning with an ENOIOCTLCMD error code
> if it is not. This ensures that ioctl calls with invalid commands are free
> of side effects, and increases the difficulty of further exploitation by
> forcing exploitation to find a way to pass a valid command first.
Here is the summary with links:
- bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
You are awesome, thank you!
Deet-doot-dot, I am a bot.
prev parent reply other threads:[~2023-04-17 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 8:02 [PATCH] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Ruihan Li
2023-04-16 8:34 ` bluez.test.bot
2023-04-17 18:30 ` patchwork-bot+bluetooth [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).