mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Aamir Ahmed <elb12345@hotmail.co.uk>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: eir: validate service data length before reading UUID
Date: Tue, 08 Sep 2026 16:30:38 +0000	[thread overview]
Message-ID: <178888503863.3627954.209106965339274612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AS8P251MB00013029B476B1D2E05DF190C8B32@AS8P251MB0001.EURP251.PROD.OUTLOOK.COM>

Hello:

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

On Mon,  7 Sep 2026 00:37:43 +0100 you wrote:
> eir_get_service_data() reads a 16-bit UUID from the service data using
> get_unaligned_le16() without first checking that the data is long enough
> to hold a UUID16 (2 bytes). If a malformed EIR entry has a service data
> field with only 1 byte of payload (field_len=2), eir_get_data() returns
> dlen=1. The subsequent get_unaligned_le16() then reads 1 byte past the
> field boundary.
> 
> [...]

Here is the summary with links:
  - Bluetooth: eir: validate service data length before reading UUID
    https://git.kernel.org/bluetooth/bluetooth-next/c/334ddae615d8

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



      reply	other threads:[~2026-09-08 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 23:37 Aamir Ahmed
2026-09-08 16:30 ` 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=178888503863.3627954.209106965339274612.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=elb12345@hotmail.co.uk \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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®