From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet
Date: Thu, 10 Oct 2024 23:30:32 +0000 [thread overview]
Message-ID: <172860303285.2203704.3221223334251807499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241009174159.15658-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 9 Oct 2024 13:41:58 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes not checking if skb really contains an ACL header otherwise
> the code may attempt to access some uninitilized/invalid memory past the
> valid skb->data.
>
> Reported-by: syzbot+6ea290ba76d8c1eb1ac2@syzkaller.appspotmail.com
> Tested-by: syzbot+6ea290ba76d8c1eb1ac2@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=6ea290ba76d8c1eb1ac2
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet
https://git.kernel.org/bluetooth/bluetooth-next/c/32fed76a03eb
- [v2,2/2] Bluetooth: hci_core: Fix not checking skb length on hci_scodata_packet
https://git.kernel.org/bluetooth/bluetooth-next/c/7285f89d6a95
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:[~2024-10-10 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 17:41 [PATCH v2 1/2] Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet Luiz Augusto von Dentz
2024-10-09 17:41 ` [PATCH v2 2/2] Bluetooth: hci_core: Fix not checking skb length on hci_scodata_packet Luiz Augusto von Dentz
2024-10-10 23: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=172860303285.2203704.3221223334251807499.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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.