From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: guhuinan <guhuinan@xiaomi.com>
Cc: linux-usb@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Ingo Rohloff <ingo.rohloff@lauterbach.com>,
Christian Brauner <brauner@kernel.org>,
Chen Ni <nichen@iscas.ac.cn>,
Peter Zijlstra <peterz@infradead.org>,
Sabyrzhan Tasbolatov <snovitoll@gmail.com>,
Akash M <akash.m5@samsung.com>, chenyu <chenyu45@xiaomi.com>,
yudongbin <yudongbin@xiaomi.com>,
mahongwei <mahongwei3@xiaomi.com>,
jiangdayu <jiangdayu@xiaomi.com>
Subject: Re: [PATCH] usb: gadget: f_fs: Fix epfile null pointer access after ep enable.
Date: Fri, 12 Sep 2025 07:32:04 +0200 [thread overview]
Message-ID: <2025091255-bluff-next-ea2b@gregkh> (raw)
In-Reply-To: <20250912040506.142146-1-guhuinan@xiaomi.com>
On Fri, Sep 12, 2025 at 12:05:06PM +0800, guhuinan wrote:
> A race condition occurs when ffs_func_eps_enable() runs concurrently
> with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset()
> sets ffs->epfiles to NULL before resetting ffs->eps_count to 0, leading
> to a NULL pointer dereference when accessing epfile->ep in
> ffs_func_eps_enable() after successful usb_ep_enable().
>
> Signed-off-by: guhuinan <guhuinan@xiaomi.com>
Please use your name, not your email alias for the From: and
signed-off-by lines.
> ---
> drivers/usb/gadget/function/f_fs.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
> index 08a251df20c4..f4aae91e7864 100644
> --- a/drivers/usb/gadget/function/f_fs.c
> +++ b/drivers/usb/gadget/function/f_fs.c
> @@ -2407,7 +2407,13 @@ static int ffs_func_eps_enable(struct ffs_function *func)
> ep = func->eps;
> epfile = ffs->epfiles;
> count = ffs->eps_count;
> - while(count--) {
> + if (!epfile) {
> + pr_err("%s: epfiles is NULL\n", __func__);
No need for this debugging line, right?
> + ret = -ENOMEM;
> + goto done;
> + }
> +
> + while (count--) {
What prevents the pointer from changing right after you check it? This
will still race :(
You need a lock somewhere to fix this properly.
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-12 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 4:05 [PATCH] usb: gadget: f_fs: Fix epfile null pointer access after ep enable guhuinan
2025-09-12 5:32 ` Greg Kroah-Hartman [this message]
2025-09-12 13:47 ` Owen Gu
2025-09-14 14:10 ` Greg Kroah-Hartman
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=2025091255-bluff-next-ea2b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akash.m5@samsung.com \
--cc=brauner@kernel.org \
--cc=chenyu45@xiaomi.com \
--cc=guhuinan@xiaomi.com \
--cc=ingo.rohloff@lauterbach.com \
--cc=jiangdayu@xiaomi.com \
--cc=linux-usb@vger.kernel.org \
--cc=mahongwei3@xiaomi.com \
--cc=nichen@iscas.ac.cn \
--cc=peterz@infradead.org \
--cc=snovitoll@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yudongbin@xiaomi.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