From: lyl2019@mail.ustc.edu.cn
To: "Sylwester Nawrocki" <snawrocki@kernel.org>
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
s.nawrocki@samsung.com, mchehab@kernel.org, krzk@kernel.org
Subject: Re: Re: [PATCH v2] media:exynos4-is: Fix a use after free in isp_video_release
Date: Tue, 27 Apr 2021 21:29:57 +0800 (GMT+08:00) [thread overview]
Message-ID: <5233bec4.64281.1791385ab97.Coremail.lyl2019@mail.ustc.edu.cn> (raw)
In-Reply-To: <a56d14d8-5be6-24ff-24f1-80274320dfe5@kernel.org>
> -----原始邮件-----
> 发件人: "Sylwester Nawrocki" <snawrocki@kernel.org>
> 发送时间: 2021-04-27 18:36:48 (星期二)
> 收件人: "Lv Yunlong" <lyl2019@mail.ustc.edu.cn>
> 抄送: linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, s.nawrocki@samsung.com, mchehab@kernel.org, krzk@kernel.org
> 主题: Re: [PATCH v2] media:exynos4-is: Fix a use after free in isp_video_release
>
> On 27.04.2021 08:02, Lv Yunlong wrote:
> > In isp_video_release, file->private_data is freed via
> > _vb2_fop_release()->v4l2_fh_release(). But the freed
> > file->private_data is still used in v4l2_fh_is_singular_file()
> > ->v4l2_fh_is_singular(file->private_data), which is a use
> > after free bug.
> >
> > My patch set file->private_data to NULL after _vb2_fop_release()
> > to avoid the use after free.
> >
> > Fixes: 34947b8aebe3f ("[media] exynos4-is: Add the FIMC-IS ISP capture DMA driver")
> > Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
> > ---
> > drivers/media/platform/exynos4-is/fimc-isp-video.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/exynos4-is/fimc-isp-video.c b/drivers/media/platform/exynos4-is/fimc-isp-video.c
> > index 612b9872afc8..2e04589068b4 100644
> > --- a/drivers/media/platform/exynos4-is/fimc-isp-video.c
> > +++ b/drivers/media/platform/exynos4-is/fimc-isp-video.c
> > @@ -315,7 +315,8 @@ static int isp_video_release(struct file *file)
> > }
> >
> > _vb2_fop_release(file, NULL);
> > -
> > + file->private_data = NULL;
>
> > if (v4l2_fh_is_singular_file(file)) {
> > fimc_pipeline_call(&ivc->ve, close);
> >
>
> Thank you for the patch. To ensure the pipeline stop call is done
> only when the last file handle is released we would need something
> as below.
>
> --------8<---------
> diff --git a/drivers/media/platform/exynos4-is/fimc-isp-video.c
> b/drivers/media/platform/exynos4-is/fimc-isp-video.c
> index 612b9872afc8..3335fec509cb 100644
> --- a/drivers/media/platform/exynos4-is/fimc-isp-video.c
> +++ b/drivers/media/platform/exynos4-is/fimc-isp-video.c
> @@ -306,17 +306,20 @@ static int isp_video_release(struct file *file)
> struct fimc_is_video *ivc = &isp->video_capture;
> struct media_entity *entity = &ivc->ve.vdev.entity;
> struct media_device *mdev = entity->graph_obj.mdev;
> + bool is_singular_file;
>
> mutex_lock(&isp->video_lock);
>
> - if (v4l2_fh_is_singular_file(file) && ivc->streaming) {
> + is_singular_file = v4l2_fh_is_singular_file(file);
> +
> + if (is_singular_file && ivc->streaming) {
> media_pipeline_stop(entity);
> ivc->streaming = 0;
> }
>
> _vb2_fop_release(file, NULL);
>
> - if (v4l2_fh_is_singular_file(file)) {
> + if (is_singular_file) {
> fimc_pipeline_call(&ivc->ve, close);
>
> mutex_lock(&mdev->graph_mutex);
> --------8<---------
>
> Regards,
> Sylwester
Ok, thanks for your review and help.
I have corrected my patch and sent the PATCH v3 for you review again.
Thanks.
prev parent reply other threads:[~2021-04-27 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 6:02 Lv Yunlong
2021-04-27 10:36 ` Sylwester Nawrocki
2021-04-27 13:29 ` lyl2019 [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=5233bec4.64281.1791385ab97.Coremail.lyl2019@mail.ustc.edu.cn \
--to=lyl2019@mail.ustc.edu.cn \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=snawrocki@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®