All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sarveshwar Bajaj <sarveshwar.bajaj@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com,
	vinit.mehta@nxp.com, mahesh.talewad@nxp.com,
	devyani.godbole@nxp.com, iulia.tanasescu@nxp.com,
	mihai-octavian.urzica@nxp.com
Subject: Re: [PATCH BlueZ v1 0/1] shared/gatt-db: Fix incorrect attribute type
Date: Mon, 24 Feb 2025 20:00:31 +0000	[thread overview]
Message-ID: <174042723126.3590450.3653149369627151708.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250221163139.1705-1-sarveshwar.bajaj@nxp.com>

Hello:

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

On Fri, 21 Feb 2025 22:01:38 +0530 you wrote:
> As part of BLE GATT Fuzzing testcase,if application sends an invalid
> ATT_FIND_BY_TYPE_VALUE_REQ with attribute type as CCC (UUID 0x2902).
> However, this request is not valid for descriptors like CCC, as it is
> specifically intended for discovering primary services with a given UUID.
> When processed in find_by_type(),attempts to access attribute->value
> without checking if attribute or attribute->value is NULL,leading to a
> segmentation fault.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/1] shared/gatt-db: Fix incorrect attribute type
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4465c577778d

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



      parent reply	other threads:[~2025-02-24 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:31 [PATCH BlueZ v1 0/1] shared/gatt-db: Fix incorrect attribute type Sarveshwar Bajaj
2025-02-21 16:31 ` [PATCH BlueZ v1 1/1] " Sarveshwar Bajaj
2025-02-21 17:38   ` bluez.test.bot
2025-02-24 20:00 ` 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=174042723126.3590450.3653149369627151708.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=devyani.godbole@nxp.com \
    --cc=iulia.tanasescu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=mahesh.talewad@nxp.com \
    --cc=mihai-octavian.urzica@nxp.com \
    --cc=sarveshwar.bajaj@nxp.com \
    --cc=vinit.mehta@nxp.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.