From: Matthew Auld <matthew.auld@intel.com>
To: Sanjay Yadav <sanjay.kumar.yadav@intel.com>,
intel-xe@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
Date: Mon, 17 Nov 2025 14:53:17 +0000 [thread overview]
Message-ID: <5fd48726-af72-4bba-9c57-9c9a198d2fa9@intel.com> (raw)
In-Reply-To: <20251117144420.2873155-2-sanjay.kumar.yadav@intel.com>
On 17/11/2025 14:44, Sanjay Yadav wrote:
> In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping
> metrics_lock. Since this lock protects the lifetime of oa_config, an
> attacker could guess the id and call xe_oa_remove_config_ioctl() with
> perfect timing, freeing oa_config before we dereference it, leading to
> a potential use-after-free.
>
> Fix this by caching the id in a local variable while holding the lock.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6614
> Fixes: cdf02fe1a94a7 ("drm/xe/oa/uapi: Add/remove OA config perf ops")
> Cc: <stable@vger.kernel.org> # v6.11+
> Suggested-by: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_oa.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> index 87a2bf53d661..8f954bc3eed5 100644
> --- a/drivers/gpu/drm/xe/xe_oa.c
> +++ b/drivers/gpu/drm/xe/xe_oa.c
> @@ -2403,11 +2403,13 @@ int xe_oa_add_config_ioctl(struct drm_device *dev, u64 data, struct drm_file *fi
> goto sysfs_err;
> }
>
> - mutex_unlock(&oa->metrics_lock);
> + id = oa_config->id;
> +
> + drm_dbg(&oa->xe->drm, "Added config %s id=%i\n", oa_config->uuid, id);
>
> - drm_dbg(&oa->xe->drm, "Added config %s id=%i\n", oa_config->uuid, oa_config->id);
> + mutex_unlock(&oa->metrics_lock);
>
> - return oa_config->id;
> + return id;
>
> sysfs_err:
> mutex_unlock(&oa->metrics_lock);
> @@ -2461,10 +2463,10 @@ int xe_oa_remove_config_ioctl(struct drm_device *dev, u64 data, struct drm_file
> sysfs_remove_group(oa->metrics_kobj, &oa_config->sysfs_metric);
> idr_remove(&oa->metrics_idr, arg);
>
> - mutex_unlock(&oa->metrics_lock);
> -
> drm_dbg(&oa->xe->drm, "Removed config %s id=%i\n", oa_config->uuid, oa_config->id);
>
> + mutex_unlock(&oa->metrics_lock);
> +
AFAICT there is not need for this change, since this path is holding a
reference to the config which is only dropped below?
> xe_oa_config_put(oa_config);
>
> return 0;
next prev parent reply other threads:[~2025-11-17 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 14:44 [PATCH] drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() Sanjay Yadav
2025-11-17 14:53 ` Matthew Auld [this message]
2025-11-18 4:06 ` Yadav, Sanjay Kumar
2025-11-17 15:06 ` ✓ CI.KUnit: success for " Patchwork
2025-11-17 15:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-17 18:56 ` ✓ Xe.CI.Full: " Patchwork
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=5fd48726-af72-4bba-9c57-9c9a198d2fa9@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sanjay.kumar.yadav@intel.com \
--cc=stable@vger.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