From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Jeongjun Park <aha310510@gmail.com>,
mchehab@kernel.org, hverkuil@kernel.org
Cc: laurent.pinchart+renesas@ideasonboard.com, crope@iki.fi,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
syzbot+6ffd76b5405c006a46b7@syzkaller.appspotmail.com,
syzbot+f1b20958f93d2d250727@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 RESEND] media: hackrf: fix to not free memory after the device is registered in hackrf_probe()
Date: Tue, 14 Oct 2025 11:51:45 +0200 [thread overview]
Message-ID: <aa78a288-0a1e-4851-a2a5-4378e96da305@kernel.org> (raw)
In-Reply-To: <20250904054232.3848637-1-aha310510@gmail.com>
Hi Jeongjun Park,
On 04/09/2025 07:42, Jeongjun Park wrote:
> In hackrf driver, the following race condition occurs:
> ```
> CPU0 CPU1
> hackrf_probe()
> kzalloc(); // alloc hackrf_dev
> ....
> v4l2_device_register();
> ....
> open("/path/to/dev"); // open hackrf dev
> ....
> v4l2_device_unregister();
> ....
> kfree(); // free hackrf_dev
> ....
> ioctl(fd, ...);
> v4l2_ioctl();
> video_is_registered() // UAF!!
> ....
> close(fd);
> v4l2_release() // UAF!!
> hackrf_video_release()
> kfree(); // DFB!!
> ```
>
> When a V4L2 or video device is unregistered, the device node is removed so
> new open() calls are blocked.
>
> However, file descriptors that are already open-and any in-flight I/O-do
> not terminate immediately; they remain valid until the last reference is
> dropped and the driver's release() is invoked.
>
> Therefore, freeing device memory on the error path after hackrf_probe()
> has registered dev it will lead to a race to use-after-free vuln, since
> those already-open handles haven't been released yet.
>
> And since release() free memory too, race to use-after-free and
> double-free vuln occur.
>
> To prevent this, if device is registered from probe(), it should be
> modified to free memory only through release() rather than calling
> kfree() directly.
>
> Cc: <stable@vger.kernel.org>
> Reported-by: syzbot+6ffd76b5405c006a46b7@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=6ffd76b5405c006a46b7
> Reported-by: syzbot+f1b20958f93d2d250727@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=f1b20958f93d2d250727
> Fixes: 8bc4a9ed8504 ("[media] hackrf: add support for transmitter")
> Signed-off-by: Jeongjun Park <aha310510@gmail.com>
> ---
> v2: Fix incorrect patch description style and CC stable mailing list
> - Link to v1: https://lore.kernel.org/all/20250822142729.1156816-1-aha310510@gmail.com/
> ---
> drivers/media/usb/hackrf/hackrf.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/media/usb/hackrf/hackrf.c b/drivers/media/usb/hackrf/hackrf.c
> index 0b50de8775a3..d7a84422193d 100644
> --- a/drivers/media/usb/hackrf/hackrf.c
> +++ b/drivers/media/usb/hackrf/hackrf.c
> @@ -1515,6 +1515,8 @@ static int hackrf_probe(struct usb_interface *intf,
> video_unregister_device(&dev->rx_vdev);
> err_v4l2_device_unregister:
> v4l2_device_unregister(&dev->v4l2_dev);
Instead of v4l2_device_unregister() this should call v4l2_device_put().
Otherwise the memory will never be freed since the v4l2_device refcount
will never reach 0.
> + dev_dbg(&intf->dev, "failed=%d\n", ret);
Drop this line, it doesn't add anything.
Regards,
Hans
> + return ret;
> err_v4l2_ctrl_handler_free_tx:
> v4l2_ctrl_handler_free(&dev->tx_ctrl_handler);
> err_v4l2_ctrl_handler_free_rx:
> --
>
prev parent reply other threads:[~2025-10-14 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 5:42 [PATCH v2 RESEND] media: hackrf: fix to not free memory after the device is registered in hackrf_probe() Jeongjun Park
2025-10-14 9:51 ` Hans Verkuil [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=aa78a288-0a1e-4851-a2a5-4378e96da305@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=aha310510@gmail.com \
--cc=crope@iki.fi \
--cc=hverkuil@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+6ffd76b5405c006a46b7@syzkaller.appspotmail.com \
--cc=syzbot+f1b20958f93d2d250727@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).