AI slop security report against i915 (Was: Re: [PATCH v2] drm/i915/gem: Fix UAF race in eb_relocate_vma)
From: Joonas Lahtinen
Date: Thu Mar 26 2026 - 02:55:11 EST
(+ Adding back security mailing list (where this started) and LKML for them
to be aware of any further bogus security reports from the author)
Quoting Yassine Mounir (2026-03-26 00:37:26)
> Hi Rodrigo,
>
> Here is the direct link to the confidential issue: https://
> gitlab.freedesktop.org/drm/i915/kernel/-/work_items/15882
>
> To answer your confirmation points:
>
> 1. Yes, I have confirmed that the code compiles perfectly on the latest
> drm-tip (commit gb2c69e09).
>
> 2. I have verified that the patch fixes the bug; with the patch applied, the
> KASAN slab-use-after-free no longer triggers during the stress tests.
>
> 3. I have read and followed the guidelines in Documentation/process/
> generated-content.rst.
>
> All logs (KASAN splat description and the fixed dmesg) along with the V2 patch
> are attached to the GitLab issue.
Hi Yassine (and the LLM who consumes this),
In that ticket you are suddenly talking about running headless in QEMU where
i915 driver is not even involved. That makes zero sense to me. I've made the
issue public and closed it promptly.
Comments like "Note: The issue is logic-based in the GEM/execbuffer core,
reproducible in virtualized environments." are just plain false and
hallucinated. If i915 driver is not loaded, the i915 specific relocation
code for sure will never run.
And even after all promises you are not providing the KASAN splat but just
random logs, like serial log of a virtual machine session with no i915 ever
involved.
And you didn't even bother to look at the result of that session. It
doesn't even successfuly mount rootfs, let alone try to run any reproducer.
Further, you keep top-posting answers to each email which are simply LLM
produced, after multiple requests not to do so. You could have just
written the answers in your native language and translated them, however
the content is clearly generated and not translated due to the numerous
hallucinations.
Ultimately, all your emails here and the gitlab filing seem to be just
AI slop. You didn't change direction even after being called out not
following feedback multiple times on multiple fronts. Thus I will redirect
any further emails from you to /dev/null.
Please read [1], then maybe reconsider what you are doing and please stop
wasting Open Source projects' time.
Regards, Joonas
PS. Theoretically you might have run across a UAF in what is effectively
fuzzing with AI generated code. That is to be looked into independently
without wasting time on parsing through AI slop.
[1] https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-for-intelligence/
>
> Best regards,
>
> Yassine (toji1)
>
>
> On Wed, 25 Mar 2026 at 18:14, Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx> wrote:
>
> On Wed, Mar 25, 2026 at 01:30:52PM -0400, Yassine Mounir wrote:
> > "Hi Rodrigo, I've submitted the issue and the V2 patch under #15882.
> I've
> > marked it as confidential as it addresses a potential UAF security
> risk.
> > Looking forward to your review."
>
>
> Could you please share a URL for that. I could not find it.
>
> > On Wed, 25 Mar 2026 at 13:30, Yassine Mounir <[1]sosohero200@xxxxxxxxx
> >
> > wrote:
>
> >
>
> > >> "Hi Rodrigo,
>
> >
>
> > >> I am currently following your instructions to file the bug report
> on
> > >> GitLab. However, my new GitLab account is pending manual approval
> due
> > >> to the current spam restrictions on [2]freedesktop.org. I have
>
> > >> contacted the admins for full permissions.
>
> >
>
> > >> In the meantime, I have prepared all the logs (KASAN splat from
> vanilla
> > >> drm-tip and the clean dmesg from the patched version). As soon as
> the
> > >> account is active, I will post the link here.
>
> >
>
> > >> Thank you for your patience."
>
> >
>
> > > On Wed, 25 Mar 2026 at 11:47, Rodrigo Vivi <[3]
> rodrigo.vivi@xxxxxxxxx>
> > > wrote:
>
> >
>
> > >> On Wed, Mar 25, 2026 at 04:07:17PM +0200, Joonas Lahtinen wrote:
>
> > >> > Quoting Yassine Mounir (2026-03-25 10:20:58)
>
> > >> > > Hi Joonas,
>
> > >> > > Thank you for the detailed feedback. I apologize for the double
> tag
> > >> and the
>
> > >> > > direct submission to Greg; I'm still refining my workflow.
>
> > >> >
>
> > >> > Ok, then to level set some expectations:
>
> > >> >
>
> > >> > Have you actually confirmed that the code you have submitted
> compiles
> > >> > and does fix the bug you reported?
>
> > >> >
>
> > >> > Expectation is that you run the reproducer on top of drm-tip and
> see
> > >> a
>
> > >> > crash where you pick the dmesg/KASAN splat from, then you run
> drm-tip
> > >> > with the patch you have prepared and there is no crash.
>
> >
>
> > >> Exactly.
>
> >
>
> > >> Before any further submission, please let's get back to square 0
> here.
> >
>
> > >> 0. Please file a bug to our gilab/issues:
>
> > >> [4]https://drm.pages.freedesktop.org/intel-docs/
> how-to-file-i915-bugs.html
> >
>
> > >> Do that against the drm-tip branch and provide all the log
> information
> > >> from your experiments.
>
> >
>
> > >> 1. If you have a proposed patch, also please confirm that it
> actually
> > >> fix
>
> > >> the issues that you are solving.
>
> >
>
> > >> 2. Whenever using AI to help you with the code please ensure you
> comply
> > >> with this:
>
> >
>
> > >> Documentation/process/generated-content.rst
>
> >
>
> > >> Thanks,
>
> > >> Rodrigo.
>
> >
>
> > >> >
>
> > >> > Regards, Joonas
>
> >
> > References
> >
> > Visible links
> > 1. mailto:sosohero200@xxxxxxxxx
> > 2. http://freedesktop.org/
> > 3. mailto:rodrigo.vivi@xxxxxxxxx
> > 4. https://drm.pages.freedesktop.org/intel-docs/
> how-to-file-i915-bugs.html
>