Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>,
	 intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v4 2/5] drm/xe/svm: Fix a potential bo UAF
Date: Wed, 26 Mar 2025 10:42:59 +0100	[thread overview]
Message-ID: <94496397d65ab85feefddaabfa02cf9531c033ec.camel@linux.intel.com> (raw)
In-Reply-To: <079ba9a9-2a31-4b73-bb9a-078e12b9ae10@intel.com>

On Wed, 2025-03-26 at 15:01 +0530, Ghimiray, Himal Prasad wrote:
> 
> 
> On 26-03-2025 13:35, Thomas Hellström wrote:
> > If drm_gpusvm_migrate_to_devmem() succeeds, if a cpu access happens
> > to the
> > range the bo may be freed before xe_bo_unlock(), causing a UAF.
> > 
> > Since the reference is transferred, use xe_svm_devmem_release() to
> > release the reference on drm_gpusvm_migrate_to_devmem() failure,
> > and hold a local reference to protect the UAF.
> 
> Fixes tag ?

Right. Will add that.

Thanks,
Thomas

> 
> > 
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> >   drivers/gpu/drm/xe/xe_svm.c | 7 +++++--
> >   1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_svm.c
> > b/drivers/gpu/drm/xe/xe_svm.c
> > index 52613dd8573a..c7424c824a14 100644
> > --- a/drivers/gpu/drm/xe/xe_svm.c
> > +++ b/drivers/gpu/drm/xe/xe_svm.c
> > @@ -702,11 +702,14 @@ static int xe_svm_alloc_vram(struct xe_vm
> > *vm, struct xe_tile *tile,
> >   	list_for_each_entry(block, blocks, link)
> >   		block->private = vr;
> >   
> > +	xe_bo_get(bo);
> >   	err = drm_gpusvm_migrate_to_devmem(&vm->svm.gpusvm,
> > &range->base,
> >   					   &bo->devmem_allocation,
> > ctx);
> > -	xe_bo_unlock(bo);
> >   	if (err)
> > -		xe_bo_put(bo);	/* Creation ref */
> > +		xe_svm_devmem_release(&bo->devmem_allocation);
> > +
> > +	xe_bo_unlock(bo);
> > +	xe_bo_put(bo);
> >   
> >   unlock:
> >   	mmap_read_unlock(mm);
> 


  reply	other threads:[~2025-03-26  9:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26  8:05 [PATCH v4 0/5] drm/xe: xe-only patches from the multi-device GPUSVM series Thomas Hellström
2025-03-26  8:05 ` [PATCH v4 1/5] drm/xe: Introduce CONFIG_DRM_XE_GPUSVM Thomas Hellström
2025-03-26  8:05 ` [PATCH v4 2/5] drm/xe/svm: Fix a potential bo UAF Thomas Hellström
2025-03-26  9:31   ` Ghimiray, Himal Prasad
2025-03-26  9:42     ` Thomas Hellström [this message]
2025-03-26  8:05 ` [PATCH v4 3/5] drm/xe/bo: Add a bo remove callback Thomas Hellström
2025-03-26  9:07   ` Matthew Auld
2025-03-26  8:05 ` [PATCH v4 4/5] drm/xe/migrate: Allow xe_migrate_vram() also on non-pagefault capable devices Thomas Hellström
2025-03-26  8:05 ` [PATCH v4 5/5] drm/xe: Make the PT code handle placement per PTE rather than per vma / range Thomas Hellström
2025-03-26  9:48   ` Ghimiray, Himal Prasad
2025-03-31 15:55   ` Lucas De Marchi
2025-04-01 11:55     ` Thomas Hellström
2025-04-01 14:04       ` Lucas De Marchi
2025-03-26  8:12 ` ✓ CI.Patch_applied: success for drm/xe: xe-only patches from the multi-device GPUSVM series (rev6) Patchwork
2025-03-26  8:12 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-26  8:14 ` ✓ CI.KUnit: success " Patchwork
2025-03-26  8:30 ` ✓ CI.Build: " Patchwork
2025-03-26  8:32 ` ✓ CI.Hooks: " Patchwork
2025-03-26  8:34 ` ✓ CI.checksparse: " Patchwork
2025-03-26  8:55 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-26 22:32 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-27  9:00 ` Patchwork
2025-03-27  9:41 ` Patchwork
2025-03-27 10:38   ` Thomas Hellström

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=94496397d65ab85feefddaabfa02cf9531c033ec.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.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