From: Greg KH <gregkh@linuxfoundation.org>
To: Yassine Mounir <sosohero200@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, joonas.lahtinen@linux.intel.com,
security@kernel.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH] drm/i915: Fix UAF race between relocation and GEM_CLOSE
Date: Tue, 24 Mar 2026 16:14:44 +0100 [thread overview]
Message-ID: <2026032401-margarine-aching-0c76@gregkh> (raw)
In-Reply-To: <CANq=4mC4ppxPYShPdQiZ6k44v5oue+NhcY8qXYBV6kEgoSWgiQ@mail.gmail.com>
On Tue, Mar 24, 2026 at 10:38:24AM -0400, Yassine Mounir wrote:
> *Hi Greg,*
Hi, but please do not top-post nor send html email, that gets dropped by
the mailing lists.
> *My apologies for the confusion. I realized I was developing against a
> distribution kernel (6.18.12-kali). I understand now why the file paths do
> not match the current upstream tree.*
>
> *Regarding the logic: The race condition happens specifically during the
> eb_relocate_entry call when a concurrent GEM_CLOSE drops the reference
> count to zero. The i915_gem_object_get is intended to pin the object's
> lifetime during this critical relocation window.*
But what happens if the object is dropped right after your call to put?
It will now be gone and not be around to work for the rest of the loop.
thnaks,
greg k-h
next prev parent reply other threads:[~2026-03-24 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 13:47 [PATCH] drm/i915: Fix UAF race between relocation and GEM_CLOSE Yassine Mounir
2026-03-24 14:26 ` Greg KH
2026-03-24 14:38 ` Yassine Mounir
2026-03-24 15:14 ` Greg KH [this message]
2026-03-24 15:25 ` Yassine Mounir
2026-03-25 16:06 ` ✗ LGCI.VerificationFailed: failure for " 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=2026032401-margarine-aching-0c76@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=security@kernel.org \
--cc=sosohero200@gmail.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