From: sashiko-bot@kernel.org
To: "Eklavya Singh" <eklavyasingh2106@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: gadgetfs: fix use-after-free after a failed bind
Date: Sun, 18 Oct 2026 16:38:36 +0000 [thread overview]
Message-ID: <sashiko-outbox-176279@kernel.org> (raw)
In-Reply-To: <20261018163434.129569-1-eklavyasingh2106@gmail.com>
> gadgetfs_bind() takes its reference on dev_data only right before it
> returns success, but its error path calls gadgetfs_unbind(), which
> always calls put_dev(). So when bind fails it drops a reference it
> never took.
>
> With ep0 open the count is 2, one for the superblock and one for the
> open file. A failed bind takes it to 1, closing ep0 frees dev_data,
> and the superblock still points at it. The next open of ep0 then takes
> dev->lock on freed memory:
>
> BUG: KASAN: slab-use-after-free in _raw_spin_lock_irq+0x3d/0x50
> gadget_dev_open+0x4b/0x1b0 drivers/usb/gadget/legacy/inode.c:1919
>
> syzbot gets there by making an allocation in bind fail, which is the
> "failed to start USB Gadget filesystem: -12" message right before the
> [ ... ]
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Reported-by: syzbot+1459655b2bf1e798f9d0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=1459655b2bf1e798f9d0
> Cc: stable@vger.kernel.org
> Signed-off-by: Eklavya Singh <eklavyasingh2106@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018163434.129569-1-eklavyasingh2106@gmail.com?part=1
next prev parent reply other threads:[~2026-10-18 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 16:34 [PATCH] usb: gadgetfs: fix use-after-free after a failed bind Eklavya Singh
2026-10-18 16:38 ` sashiko-bot [this message]
2026-10-18 16:38 ` 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=sashiko-outbox-176279@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eklavyasingh2106@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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