From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Alexander Aring <aahringo@redhat.com>, cve@kernel.org
Cc: David Teigland <teigland@redhat.com>,
gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
gregkh@kernel.org
Subject: Re: [PATCH v2] dlm: fix buffer overflow from negative len in dlm_search_rsb_tree
Date: Wed, 27 May 2026 09:01:38 +0800 [thread overview]
Message-ID: <464dd360-f4b9-4c47-90ac-2d1f558814a9@linux.alibaba.com> (raw)
In-Reply-To: <CAK-6q+hPM=+fXkPSbr60Y6S1O_RfYGBUeL3mfVu0H1ymZ0gp6w@mail.gmail.com>
On 5/26/26 9:58 PM, 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.
>
> There is another patch required for CVE-2026-43125 [0].
>
> Joseph I think for v3 you should cc also cve@kernel.org and mention
> this in your commit msg.
>
This is indeed found when I backport this CVE into our tree.
But I think it is a different case so I just send to upstream first.
Thanks,
Joseph
next prev parent reply other threads:[~2026-05-27 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 2:03 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
2026-05-27 1:01 ` Joseph Qi [this message]
2026-05-29 13:19 ` Alexander Aring
2026-07-16 18:27 ` 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=464dd360-f4b9-4c47-90ac-2d1f558814a9@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=aahringo@redhat.com \
--cc=cve@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=gregkh@kernel.org \
--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
all inboxes | Powered by JetHome®