From: "Nair, Jayapal Ashwin" <jayapalashwin.nair@amd.com>
To: Maaz Mombasawala <maaz.mombasawala@broadcom.com>,
dri-devel@lists.freedesktop.org, zack.rusin@broadcom.com
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch
Subject: Re: [PATCH] drm/vmwgfx: Fix use-after-free race in vmw_dumb_create()
Date: Fri, 30 Oct 2026 11:23:29 +0530 [thread overview]
Message-ID: <7a822adb-ddb5-4338-8949-3ccb0942e0a0@amd.com> (raw)
In-Reply-To: <DMHS7SIDIUGJ.168385UCMC4QI@broadcom.com>
On 30-10-2026 06:59, Maaz Mombasawala <maaz.mombasawala@broadcom.com> wrote:
> How is userspace able to see the gem handle to call DRM_IOCTL_GEM_CLOSE
> on it before DRM_IOCTL_MODE_CREATE_DUMB has returned it?
>
The handle is installed in file_priv->object_idr by
drm_gem_handle_create() inside vmw_gb_surface_define_ext_ioctl(), before
DRM_IOCTL_MODE_CREATE_DUMB returns it, and GEM handles are predictable:
idr_alloc() hands out the lowest free id starting at 1. On a freshly
opened fd the dumb buffer gets handle 1, so a second thread on the same
fd can spin on DRM_IOCTL_GEM_CLOSE(1), getting -EINVAL until the handle
appears. Once closed, id 1 is free again, so the race can be retried
indefinitely.
I tried this methodology and got a KASAN splat:
BUG: KASAN: slab-use-after-free in vmw_dumb_create+0x705/0x850
Read of size 8 at addr ffff88810fd5b2d0 by task poc/228
...
Allocated by task 228:
__kmalloc_cache_noprof+0x166/0x3b0
vmw_bo_create+0xbc/0x660
vmw_gem_object_create_with_handle+0xf9/0x190
vmw_gb_surface_define_internal.constprop.0+0xe23/0x17c0
vmw_dumb_create+0x415/0x850
...
Freed by task 228:
kfree+0x216/0x450
vmw_bo_free+0x414/0x640
ttm_bo_release+0x3bc/0x9a0
vmw_dumb_create+0x6d9/0x850
...
The buggy address belongs to the object at ffff88810fd5b000
which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 720 bytes inside of
freed 1024-byte region [ffff88810fd5b000, ffff88810fd5b400)
...
BUG: unable to handle page fault for address: ffffffffffffffb0
#PF: supervisor write access in kernel mode
RIP: 0010:vmw_dumb_create+0x667/0x850
R12: 0000000000000000
Kernel panic - not syncing: Fatal exception
The read is vbo->dumb_surface (offset 0x2d0); it comes back NULL and the
subsequent usurf->prime.base.refcount_release = NULL store faults at
NULL - 0x50.
> --
> Maaz Mombasawala <maaz.mombasawala@broadcom.com>
>
prev parent reply other threads:[~2026-10-30 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 5:21 Jayapal Ashwin Nair
2026-10-30 1:29 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
2026-10-30 5:53 ` Nair, Jayapal Ashwin [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=7a822adb-ddb5-4338-8949-3ccb0942e0a0@amd.com \
--to=jayapalashwin.nair@amd.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maaz.mombasawala@broadcom.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@broadcom.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
all inboxes | Powered by JetHome®