mirror of https://lore.kernel.org/lkml/
 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,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: eir: Fix OOB read in eir_get_service_data()
Date: Mon, 17 Aug 2026 19:46:06 +0000	[thread overview]
Message-ID: <178699596638.1691257.16551460626446632057.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260815062419.37489-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 Sat, 15 Aug 2026 15:24:19 +0900 you wrote:
> eir_get_service_data() walks the advertising data for a Service Data
> field with a matching UUID.  On a mismatch it advances:
> 
>     eir += dlen;
>     eir_len -= dlen;
> 
> eir_get_data() reports dlen as the field's data length, but the field
> spans dlen + 2 bytes once its length and type bytes count, and more
> when non-Service-Data fields were skipped to reach it.  The pointer
> lands correctly on the next field.  eir_len does not, and the shortfall
> compounds across fields until eir_get_data() reads the length and type
> bytes of a "field" past the end of the buffer.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: eir: Fix OOB read in eir_get_service_data()
    https://git.kernel.org/bluetooth/bluetooth-next/c/14a97a38ba8f

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



      reply	other threads:[~2026-08-17 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15  6:24 HyeongJun An
2026-08-17 19:46 ` 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=178699596638.1691257.16551460626446632057.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 \
    --cc=stable@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

all inboxes | Powered by JetHome®