From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Breno Leitao <leitao@debian.org>
Cc: stable@kernel.org, Sasha Levin <sashal@kernel.org>,
Corey Minyard <corey@minyard.net>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Vlad Poenaru <thevlad@meta.com>,
kernel-team@meta.com, stable@vger.kernel.org
Subject: Re: [PATCH stable] ipmi: Fix use-after-free and list corruption on sender error
Date: Mon, 9 Mar 2026 11:34:08 +0100 [thread overview]
Message-ID: <2026030953-imaging-resize-ce85@gregkh> (raw)
In-Reply-To: <20260309-ipmi_stable-v1-1-be09c9686671@debian.org>
On Mon, Mar 09, 2026 at 03:16:13AM -0700, Breno Leitao wrote:
> From: Corey Minyard <corey@minyard.net>
>
> [ Upstream commit f9323a44994c2ccd5e0d582bac6f2b2a662e5603 ]
This is not a valid git id in Linus's tree :(
next prev parent reply other threads:[~2026-03-09 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 10:16 [PATCH stable] ipmi: Fix use-after-free and list corruption on sender error Breno Leitao
2026-03-09 10:34 ` Greg Kroah-Hartman [this message]
2026-03-09 10:52 ` Breno Leitao
2026-03-09 11:07 ` Greg Kroah-Hartman
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=2026030953-imaging-resize-ce85@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corey@minyard.net \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=sashal@kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thevlad@meta.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