From: Jean Delvare <jdelvare@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable] EDAC/mc: Really fix error path ordering in edac_mc_alloc()
Date: Wed, 4 Nov 2026 07:20:24 +0100 [thread overview]
Message-ID: <20261104072024.24f77132@endymion> (raw)
In-Reply-To: <20261103210951.GAaupNn1kEIZMr4GVt@fat_crate.local>
On Tue, 3 Nov 2026 13:09:51 -0800, Borislav Petkov wrote:
> On Tue, Nov 03, 2026 at 05:04:39PM +0100, Jean Delvare wrote:
> > The backport of 51520e03e70d ("EDAC/mc: Fix error path ordering in
> > edac_mc_alloc()") to stable kernel branches is incomplete due to a
> > different memory allocation scheme. In v6.19 and earlier, the device
> > initialization must be moved further up so that all jumps to the
> > error label are covered.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: stable@kernel.org # v6.19-
>
> looks about right:
>
> Acked-by: Borislav Petkov (AMD) <bp@alien8.de>
Thanks for the review.
> > I believe that CVE-2026-31689 is not properly fixed in kernels v6.19 and
> > older as of today, and the patch below shall address that. Affected
> > branches still under maintenance would be v6.18, v6.12, v6.6 and v6.1.
> > v6.19 is equally affected but no longer maintained.
>
> Have you audited all those other trees, whether backporting it there is
> correct?
Yes I did.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2026-11-04 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 16:04 [PATCH stable] EDAC/mc: Really fix error path ordering in edac_mc_alloc() Jean Delvare
2026-11-03 21:09 ` Borislav Petkov
2026-11-04 6:20 ` Jean Delvare [this message]
2026-11-04 15:03 ` Sasha Levin
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=20261104072024.24f77132@endymion \
--to=jdelvare@suse.de \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.