From: patchwork-bot+bluetooth@kernel.org
To: Ildar Kamaletdinov <i.kamaletdinov@omp.ru>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/6] [v4] Fix bugs found by SVACE static analisys tool
Date: Mon, 04 Apr 2022 17:14:24 +0000 [thread overview]
Message-ID: <164909246433.14329.9969531326038697330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220401121647.3985682-1-i.kamaletdinov@omp.ru>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 1 Apr 2022 15:16:41 +0300 you wrote:
> This patch set includes few fixes that was found by Linux Verification Center
> (linuxtesting.org) with the SVACE static analysis tool.
>
> I have manually filtered out non-relevant and false positive problems and only
> procedeed with bugs that currently lead to some errors/vulnerabilities or may
> lead to them in some specific conditions.
>
> [...]
Here is the summary with links:
- [BlueZ,1/6] monitor: Fix out-of-bound read in print_le_states
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7fdfb67284a2
- [BlueZ,2/6] tools: Fix buffer overflow in hciattach_tialt.c
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d328abaa1715
- [BlueZ,3/6] tools: Fix signed integer overflow in btsnoop.c
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=497a0b220dbd
- [BlueZ,4/6] tools: Limit width of fields in sscanf
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1e664b9838cd
- [BlueZ,5/6] device: Limit width of fields in sscanf
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4afbef7790ce
- [BlueZ,6/6] gatt: Fix double free and freed memory dereference
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3627eddea130
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:[~2022-04-04 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 12:16 [PATCH BlueZ 0/6] [v4] Fix bugs found by SVACE static analisys tool Ildar Kamaletdinov
2022-04-01 12:16 ` [PATCH BlueZ 1/6] monitor: Fix out-of-bound read in print_le_states Ildar Kamaletdinov
2022-04-01 16:00 ` Fix bugs found by SVACE static analisys tool bluez.test.bot
2022-04-01 12:16 ` [PATCH BlueZ 2/6] tools: Fix buffer overflow in hciattach_tialt.c Ildar Kamaletdinov
2022-04-01 12:16 ` [PATCH BlueZ 3/6] tools: Fix signed integer overflow in btsnoop.c Ildar Kamaletdinov
2022-04-01 12:16 ` [PATCH BlueZ 4/6] tools: Limit width of fields in sscanf Ildar Kamaletdinov
2022-04-01 12:16 ` [PATCH BlueZ 5/6] device: " Ildar Kamaletdinov
2022-04-01 12:16 ` [PATCH BlueZ 6/6] gatt: Fix double free and freed memory dereference Ildar Kamaletdinov
2022-04-04 17:14 ` 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=164909246433.14329.9969531326038697330.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=i.kamaletdinov@omp.ru \
--cc=linux-bluetooth@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 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.