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
Subject: Re: [PATCH BlueZ v2 0/1] Fix null pointer dereference in util_ltv_foreach
Date: Tue, 25 Jun 2024 14:10:30 +0000 [thread overview]
Message-ID: <171932463081.10330.9812126766830035655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240621075517.22576-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 Jun 2024 13:25:16 +0530 you wrote:
> In the existing code, iov structure is initialized with iov.iov_base = (void *)
> data. If data is NULL,casting (void *) NULL to iov_base results in a null
> pointer dereference.Inside the loop of util_ltv_foreach,
> util_iov_pull_u8(&iov, &l) is called to pull uint8_t values from iov.
> If iov.iov_base (derived from data) is NULL,attempting to dereference it in
> util_iov_pull_u8 will cause a segmentation fault.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/1] shared/util: Fix null pointer dereference in util_ltv_foreach()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e453627223db
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-06-25 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:55 [PATCH BlueZ v2 0/1] Fix null pointer dereference in util_ltv_foreach Sarveshwar Bajaj
2024-06-21 7:55 ` [PATCH BlueZ v2 1/1] shared/util: Fix null pointer dereference in util_ltv_foreach() Sarveshwar Bajaj
2024-06-21 9:47 ` Fix null pointer dereference in util_ltv_foreach bluez.test.bot
2024-06-25 14:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 6:43 [PATCH BlueZ v2 0/1] " Sarveshwar Bajaj
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=171932463081.10330.9812126766830035655.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devyani.godbole@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=mahesh.talewad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox