From: Johan Hovold <johan@kernel.org>
To: Adriano Cordova <adrianox@gmail.com>
Cc: Ulf Hansson <ulfh@kernel.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+f312381a95cc080992fd@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] mmc: vub300: fix use-after-free in vub300 teardown
Date: Tue, 8 Sep 2026 09:26:10 +0200 [thread overview]
Message-ID: <ap-4khETBju3X8-T@hovoldconsulting.com> (raw)
In-Reply-To: <20260907151428.643841-1-adrianox@gmail.com>
On Mon, Sep 07, 2026 at 12:14:28PM -0300, Adriano Cordova wrote:
> Do not dereference mmc/vub300/udev after the final kref_put, because
> it can release them via mmc_free_host()/usb_put_dev().
>
> Fixes: 8f4d20a71022 ("mmc: vub300: fix use-after-free on disconnect")
This commit reverted a buggy change so if anything is broken here, this
isn't the commit to blame.
> Reported-by: syzbot+f312381a95cc080992fd@syzkaller.appspotmail.com
> Link: https://syzkaller.appspot.com/bug?extid=f312381a95cc080992fd
> Cc: stable@vger.kernel.org
> Signed-off-by: Adriano Cordova <adrianox@gmail.com>
Are you missing an Assisted-by tag?
> ---
> drivers/mmc/host/vub300.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/host/vub300.c b/drivers/mmc/host/vub300.c
> index 2dae474dcd06..a1a6aa1aafdb 100644
> --- a/drivers/mmc/host/vub300.c
> +++ b/drivers/mmc/host/vub300.c
> @@ -370,13 +370,14 @@ static void vub300_delete(struct kref *kref)
> { /* kref callback - softirq */
> struct vub300_mmc_host *vub300 = kref_to_vub300_mmc_host(kref);
> struct mmc_host *mmc = vub300->mmc;
> + struct usb_device *udev = vub300->udev;
>
> usb_free_urb(vub300->command_out_urb);
> vub300->command_out_urb = NULL;
> usb_free_urb(vub300->command_res_urb);
> vub300->command_res_urb = NULL;
> - usb_put_dev(vub300->udev);
> mmc_free_host(mmc);
> + usb_put_dev(udev);
This makes no sense at all as the driver data is freed by
mmc_free_host().
> /*
> * and hence also frees vub300
> * which is contained at the end of struct mmc
> @@ -1794,8 +1795,8 @@ static void vub300_cmndwork_thread(struct work_struct *work)
> construct_request_response(vub300, cmd);
> vub300->resp_len = 0;
> mutex_unlock(&vub300->cmd_mutex);
> - kref_put(&vub300->kref, vub300_delete);
> mmc_request_done(vub300->mmc, req);
> + kref_put(&vub300->kref, vub300_delete);
This order has been here since the driver was merged.
> return;
> }
> }
> @@ -1946,8 +1947,8 @@ static void vub300_mmc_request(struct mmc_host *mmc, struct mmc_request *req)
> satisfy_request_from_offloaded_data(vub300, cmd)) {
> cmd->error = 0;
> mutex_unlock(&vub300->cmd_mutex);
> - kref_put(&vub300->kref, vub300_delete);
> mmc_request_done(mmc, req);
> + kref_put(&vub300->kref, vub300_delete);
Same here.
So if this is wrong (it does look suspicious, but this driver is just a
mess) then that's the commit to blame.
> return;
> } else {
> vub300->cmd = cmd;
Johan
next prev parent reply other threads:[~2026-09-08 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 15:14 Adriano Cordova
2026-09-08 7:26 ` Johan Hovold [this message]
2026-09-08 13:28 ` Adriano Córdova
2026-09-08 13:51 ` Johan Hovold
2026-09-08 15:08 ` Adriano Córdova
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=ap-4khETBju3X8-T@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=adrianox@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+f312381a95cc080992fd@syzkaller.appspotmail.com \
--cc=ulfh@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 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®