From: "Christian König" <christian.koenig@amd.com>
To: Min Li <lm0963hack@gmail.com>, alexander.deucher@amd.com
Cc: Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
sumit.semwal@linaro.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v2] drm/radeon: fix race condition UAF in radeon_gem_set_domain_ioctl
Date: Mon, 5 Jun 2023 10:12:52 +0200 [thread overview]
Message-ID: <e337dec6-0b0e-7e53-e38d-ae1791b98418@amd.com> (raw)
In-Reply-To: <20230603074345.17907-1-lm0963hack@gmail.com>
Am 03.06.23 um 09:43 schrieb Min Li:
> Userspace can race to free the gobj(robj converted from), robj should not
> be accessed again after drm_gem_object_put, otherwith it will result in
> use-after-free.
>
> Signed-off-by: Min Li <lm0963hack@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> Changes in v2:
> - Remove unused robj, avoid compile complain
>
> drivers/gpu/drm/radeon/radeon_gem.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_gem.c b/drivers/gpu/drm/radeon/radeon_gem.c
> index bdc5af23f005..d3f5ddbc1704 100644
> --- a/drivers/gpu/drm/radeon/radeon_gem.c
> +++ b/drivers/gpu/drm/radeon/radeon_gem.c
> @@ -459,7 +459,6 @@ int radeon_gem_set_domain_ioctl(struct drm_device *dev, void *data,
> struct radeon_device *rdev = dev->dev_private;
> struct drm_radeon_gem_set_domain *args = data;
> struct drm_gem_object *gobj;
> - struct radeon_bo *robj;
> int r;
>
> /* for now if someone requests domain CPU -
> @@ -472,13 +471,12 @@ int radeon_gem_set_domain_ioctl(struct drm_device *dev, void *data,
> up_read(&rdev->exclusive_lock);
> return -ENOENT;
> }
> - robj = gem_to_radeon_bo(gobj);
>
> r = radeon_gem_set_domain(gobj, args->read_domains, args->write_domain);
>
> drm_gem_object_put(gobj);
> up_read(&rdev->exclusive_lock);
> - r = radeon_gem_handle_lockup(robj->rdev, r);
> + r = radeon_gem_handle_lockup(rdev, r);
> return r;
> }
>
next prev parent reply other threads:[~2023-06-05 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 7:43 [PATCH v2] drm/radeon: fix race condition UAF in radeon_gem_set_domain_ioctl Min Li
2023-06-05 8:12 ` Christian König [this message]
2023-06-05 15:21 ` Alex Deucher
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=e337dec6-0b0e-7e53-e38d-ae1791b98418@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lm0963hack@gmail.com \
--cc=sumit.semwal@linaro.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