From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, "Maíra Canal" <mcanal@igalia.com>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Iago Toral Quiroga <itoral@igalia.com>,
kernel-dev@igalia.com
Subject: Re: [PATCH 6.12.y 1/2] drm/v3d: Fix use-after-free of CPU job query arrays on error path
Date: Tue, 2 Jun 2026 14:21:22 -0400 [thread overview]
Message-ID: <20260602180900.drm-v3d-uaf-reply@kernel.org> (raw)
In-Reply-To: <20260531210323.1637818-1-mcanal@igalia.com>
On Sat, May 31, 2026 at 06:02:01PM -0300, Maíra Canal wrote:
> [PATCH 6.12.y 1/2] drm/v3d: Fix use-after-free of CPU job query arrays on error path
> [PATCH 6.12.y 2/2] drm/v3d: Release indirect CSD GEM reference on CPU job free
Both patches now applied to 6.12.y.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-02 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 21:02 [PATCH 6.12.y 1/2] drm/v3d: Fix use-after-free of CPU job query arrays on error path Maíra Canal
2026-05-31 21:02 ` [PATCH 6.12.y 2/2] drm/v3d: Release indirect CSD GEM reference on CPU job free Maíra Canal
2026-06-02 18:21 ` Sasha Levin [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=20260602180900.drm-v3d-uaf-reply@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=itoral@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=mcanal@igalia.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