All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: HyeongJun An <sammiee5311@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: virtio_bt: avoid OOB read of build info string in virtbt_setup_zephyr()
Date: Fri, 31 Jul 2026 18:50:07 +0000	[thread overview]
Message-ID: <178552380763.861446.6322185394985227268.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715121628.1590321-1-sammiee5311@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 15 Jul 2026 21:16:28 +0900 you wrote:
> virtbt_setup_zephyr() sends the Zephyr vendor command 0xfc08 (Read Build
> Information) and passes the response to bt_dev_info() and hci_set_fw_info()
> as a "%s" string starting at skb->data + 1, without checking the length:
> 
>   bt_dev_info(hdev, "%s", (char *)(skb->data + 1));
>   hci_set_fw_info(hdev, "%s", skb->data + 1);
> 
> [...]

Here is the summary with links:
  - Bluetooth: virtio_bt: avoid OOB read of build info string in virtbt_setup_zephyr()
    https://git.kernel.org/bluetooth/bluetooth-next/c/d264c90ca22e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-31 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 12:16 [PATCH] Bluetooth: virtio_bt: avoid OOB read of build info string in virtbt_setup_zephyr() HyeongJun An
2026-07-15 13:43 ` bluez.test.bot
2026-07-30  1:57 ` [PATCH v2] Bluetooth: virtio_bt: avoid OOB read of build info string HyeongJun An
2026-07-30  4:40   ` [v2] " bluez.test.bot
2026-07-31 18:50   ` [PATCH v2] " patchwork-bot+bluetooth
2026-07-31 18:50 ` patchwork-bot+bluetooth [this message]

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=178552380763.861446.6322185394985227268.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=sammiee5311@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.