From: patchwork-bot+bluetooth@kernel.org
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@intel.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()
Date: Mon, 16 Mar 2026 20:00:07 +0000 [thread overview]
Message-ID: <177369120703.3291233.5058198954118841523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <abMgjwF9IdkNhmpF@v4bel>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 13 Mar 2026 05:22:39 +0900 you wrote:
> l2cap_ecred_data_rcv() reads the SDU length field from skb->data using
> get_unaligned_le16() without first verifying that skb contains at least
> L2CAP_SDULEN_SIZE (2) bytes. When skb->len is less than 2, this reads
> past the valid data in the skb.
>
> The ERTM reassembly path correctly calls pskb_may_pull() before reading
> the SDU length (l2cap_reassemble_sdu, L2CAP_SAR_START case). Apply the
> same validation to the Enhanced Credit Based Flow Control data path.
>
> [...]
Here is the summary with links:
- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()
https://git.kernel.org/bluetooth/bluetooth-next/c/a480f2bbc7c2
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-03-16 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:22 [PATCH] Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() Hyunwoo Kim
2026-03-12 20:52 ` bluez.test.bot
2026-03-16 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=177369120703.3291233.5058198954118841523.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=imv4bel@gmail.com \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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