From: Greg KH <gregkh@linuxfoundation.org>
To: Hui Peng <benquike@gmail.com>
Cc: arve@android.com, tkjos@android.com, brauner@kernel.org,
cmllamas@google.com, aliceryhl@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binder: fix sender fd 0 close and file refcount leak on TF_UPDATE_TXN
Date: Sun, 20 Sep 2026 06:00:56 +0100 [thread overview]
Message-ID: <2026092016-sphinx-turkey-1be6@gregkh> (raw)
In-Reply-To: <20260919213648.3316566-1-benquike@gmail.com>
On Sat, Sep 19, 2026 at 09:36:48PM +0000, Hui Peng wrote:
> In `binder_proc_transaction()`, when a oneway transaction with
> `TF_UPDATE_TXN` supersedes an outdated pending transaction
> (`t_outdated`), the driver calls `binder_release_entire_buffer(proc,
> NULL, buffer, false)` and `kfree(t_outdated)`.
>
> Passing `is_failure = false` while `buffer->transaction` has already
> been set to `NULL` causes two bugs when `t_outdated` contained
> `BINDER_TYPE_FDA` or `BINDER_TYPE_FD` objects:
>
> 1. For `BINDER_TYPE_FDA`, `binder_translate_fd_array()` never wrote
> recipient file descriptors into the buffer (it only appended `struct
> file *` entries to `t_outdated->fd_fixups`), so the FD array in
> `buffer` still contains zeros (or sender-supplied offsets). Because
> `is_failure` is `false`, `binder_transaction_buffer_release()`
> executes the `!is_failure` branch on `BINDER_TYPE_FDA` and calls
> `binder_deferred_fd_close(fd)` (closing `fd 0` in `current->files`,
> which is the **sender** process!).
> 2. `t_outdated` is freed via `kfree(t_outdated)` without calling
> `binder_free_txn_fixups(t_outdated)`, permanently leaking every
> translated `struct file` reference in `t_outdated->fd_fixups`.
>
> Pass `is_failure = true` to `binder_release_entire_buffer()` and call
> `binder_free_txn_fixups(t_outdated)` before freeing `t_outdated`.
Please delete all LLM-generated changelog text and rewrite it in your
own words to explain the problem and why this patch is needed (same for
your other 6 patches). Also, how were these all tested?
thanks,
greg k-h
prev parent reply other threads:[~2026-09-20 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 21:36 Hui Peng
2026-09-20 5:00 ` Greg KH
2026-09-20 5:00 ` Greg KH [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=2026092016-sphinx-turkey-1be6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=benquike@gmail.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tkjos@android.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®