gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@kernel.org>
To: Alexander Aring <aahringo@redhat.com>
Cc: Joseph Qi <joseph.qi@linux.alibaba.com>,
	cve@kernel.org, David Teigland <teigland@redhat.com>,
	gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dlm: fix buffer overflow from negative len in dlm_search_rsb_tree
Date: Sat, 30 May 2026 09:36:11 +0200	[thread overview]
Message-ID: <2026053054-democracy-mower-0a5f@gregkh> (raw)
In-Reply-To: <CAK-6q+ibs=hWiCPGKNdELdgiqq5kpmwDfUJdMTQkbrGGP4yHUA@mail.gmail.com>

On Fri, May 29, 2026 at 09:24:59AM -0400, Alexander Aring wrote:
> Hi,
> 
> On Tue, May 26, 2026 at 12:09 PM Greg KH <gregkh@kernel.org> wrote:
> >
> > On Tue, May 26, 2026 at 09:58:32AM -0400, Alexander Aring wrote:
> > > Hi,
> > >
> > > On Mon, May 25, 2026 at 1:39 PM Alexander Aring <aahringo@redhat.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Mon, May 25, 2026 at 10:27 AM Alexander Aring <aahringo@redhat.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > On Sat, May 16, 2026 at 10:03 PM Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
> > > > > >
> > > > > > commit 080e5563f878 only checks for len > DLM_RESNAME_MAXLEN, which does
> > > > >
> > > > > check with checkpath, it reports an error regarding how this commit
> > > > > reference is done.
> > > > >
> > > >
> > > > This also addresses CVE-2026-43125 [0].
> > > >
> > > > - Alex
> > > >
> > > > [0] https://lore.kernel.org/linux-cve-announce/2026050619-CVE-2026-43125-c9f9@gregkh/
> > >
> > > cc the right folks cve@kernel.org as described in the kernel documentation.
> >
> > For what?
> >
> 
> because
> 
> "If the CVE assignment team misses a specific fix that any user feels
> should have a CVE assigned to it, please email them at
> <cve@kernel.org> and the team there will work with you on it." [0]
> 
> The initial fix did not resolve CVE-2026-43125, there are additional
> changes are required.

That CVE describes the specific issue that that patch fixes.  If there
are additional issues that this patch does not resolve, then it deserves
a new CVE for the new fix, OR you should add the new sha1 to the old CVE
entry.

Where is the new fix?

thanks,

greg k-h

  reply	other threads:[~2026-05-30 10:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  2:03 [PATCH v2] dlm: fix buffer overflow from negative len in dlm_search_rsb_tree Joseph Qi
2026-05-25 14:27 ` Alexander Aring
2026-05-25 17:39   ` Alexander Aring
2026-05-26 13:58     ` Alexander Aring
2026-05-26 16:08       ` Greg KH
2026-05-29 13:24         ` Alexander Aring
2026-05-30  7:36           ` Greg KH [this message]
2026-05-27  1:01       ` Joseph Qi
2026-05-29 13:19         ` Alexander Aring

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=2026053054-democracy-mower-0a5f@gregkh \
    --to=gregkh@kernel.org \
    --cc=aahringo@redhat.com \
    --cc=cve@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teigland@redhat.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