From: Rahul Samana <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] db4489: gobex: Fix use-after-free when cancelling SRM PUT ...
Date: Tue, 07 Jul 2026 01:38:03 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1122826/000000-db4489@github.com> (raw)
Branch: refs/heads/1122826
Home: https://github.com/bluez/bluez
Commit: db448996954c22418d44421f704812cb891a6ae6
https://github.com/bluez/bluez/commit/db448996954c22418d44421f704812cb891a6ae6
Author: Rahul Samana <rahul.samana@oss.qualcomm.com>
Date: 2026-07-07 (Tue, 07 Jul 2026)
Changed paths:
M gobex/gobex.c
Log Message:
-----------
gobex: Fix use-after-free when cancelling SRM PUT transfer
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.
Fix by clearing pending_req->rsp_func if it belongs to the same
transfer being cancelled.
Signed-off-by: Rahul Samana <rahul.samana@oss.qualcomm.com>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-07 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1122826/000000-db4489@github.com \
--to=noreply@github.com \
--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.