Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Piyus Kedia <piyus@iiitd.ac.in>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	kapil@presceralabs.ai
Subject: Re: [PATCH] Bluetooth: L2CAP: clear the SDU before the receive callback
Date: Mon, 16 Nov 2026 19:50:05 +0000	[thread overview]
Message-ID: <179485860503.3856541.15241820341597541824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112173812.18696-2-piyus@iiitd.ac.in>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 12 Nov 2026 23:08:12 +0530 you wrote:
> l2cap_ecred_data_rcv() completes a reassembled SDU by calling
> l2cap_ecred_recv() with chan->sdu still set, and only clears the
> reassembly state after it returns:
> 
> 	if (chan->sdu->len == chan->sdu_len) {
> 		err = l2cap_ecred_recv(chan, chan->sdu);
> 		if (!err) {
> 			chan->sdu = NULL;
> 			...
> 
> [...]

Here is the summary with links:
  - Bluetooth: L2CAP: clear the SDU before the receive callback
    https://git.kernel.org/bluetooth/bluetooth-next/c/76248359ac32

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-16 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 17:38 [BUG] Bluetooth: L2CAP: slab-use-after-free reading chan->sdu->len after the receive callback has consumed the SDU (seen on 7.3.1) Piyus Kedia
2026-11-12 17:38 ` [PATCH] Bluetooth: L2CAP: clear the SDU before the receive callback Piyus Kedia
2026-11-12 19:54   ` Luiz Augusto von Dentz
2026-11-13 16:20     ` Piyus Kedia
2026-11-13 16:23       ` Luiz Augusto von Dentz
2026-11-13 16:32         ` Piyus Kedia
2026-11-16 19:50   ` 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=179485860503.3856541.15241820341597541824.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=kapil@presceralabs.ai \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=piyus@iiitd.ac.in \
    /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