All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Rahul Samana <rahul.samana@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, quic_mohamull@quicinc.com,
	quic_hbandi@quicinc.com, quic_anubhavg@quicinc.com
Subject: Re: [PATCH v1] gobex: Fix use-after-free when cancelling SRM PUT transfer
Date: Thu, 09 Jul 2026 15:30:16 +0000	[thread overview]
Message-ID: <178361101613.3546291.5670165280886865738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707063543.80320-1-rahul.samana@oss.qualcomm.com>

Hello:

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

On Tue,  7 Jul 2026 12:05:43 +0530 you wrote:
> In SRM mode put_get_data() queues the next packet during encoding of
> the current one, so transfer->req_id and pending_req->id can diverge.
> When g_obex_cancel_transfer() cancels the queued packet from tx_queue,
> cancel_complete() frees the transfer while pending_req still holds a
> callback pointing to it. Its G_OBEX_DEFAULT_TIMEOUT (10s) then fires
> on freed memory causing a SIGSEGV.
> 
> [...]

Here is the summary with links:
  - [v1] gobex: Fix use-after-free when cancelling SRM PUT transfer
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9e9f0a370c59

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-07-09 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  6:35 [PATCH v1] gobex: Fix use-after-free when cancelling SRM PUT transfer Rahul Samana
2026-07-07  9:24 ` [v1] " bluez.test.bot
2026-07-09 15: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=178361101613.3546291.5670165280886865738.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_anubhavg@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.com \
    --cc=rahul.samana@oss.qualcomm.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.