From: patchwork-bot+bluetooth@kernel.org
To: Pavel Shpakovskiy <pashpakovskii@salutedevices.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, avkrasnov@salutedevices.com,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@salutedevices.com,
rulkc@linuxtesting.org, linux-amlogic@lists.landau.one
Subject: Re: [PATCH v2] Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference
Date: Tue, 11 Aug 2026 20:10:21 +0000 [thread overview]
Message-ID: <178647902138.1134064.3407354756099050470.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808163128.288740-1-pashpakovskii@salutedevices.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 8 Aug 2026 19:31:11 +0300 you wrote:
> 'uuid_count' member of struct 'discovery_state' is assigned and read
> without any locks, so there is a chance of situation when
> uuid_count != 0, but uuids is NULL and there will be NULL pointer
> dereference.
>
> Possible race:
> 'hci_update_passive_scan_sync'
> 'hci_discovery_filter_clear'
> hdev->discovery.uuid_count = 0;
> <----------------------preempted----------------------------->
> 'start_service_discovery'
> // Set uuid_count to value != 0
> hdev->discovery.uuid_count = uuid_count;
> hdev->discovery.uuids = kmemdup(...);
> <----------------------preempted----------------------------->
> spin_lock(&hdev->discovery.lock);
> kfree(hdev->discovery.uuids);
> hdev->discovery.uuids = NULL;
> spin_unlock(&hdev->discovery.lock);
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference
https://git.kernel.org/bluetooth/bluetooth-next/c/99672791e9c9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-11 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 16:31 [PATCH v2] Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference Pavel Shpakovskiy
2026-08-11 20:10 ` 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=178647902138.1134064.3407354756099050470.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@salutedevices.com \
--cc=kuba@kernel.org \
--cc=linux-amlogic@lists.landau.one \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pashpakovskii@salutedevices.com \
--cc=rulkc@linuxtesting.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