From: Martin Wilck <mwilck@suse.com>
To: miaoguanqin <miaoguanqin@huawei.com>,
Jes Sorensen <jes@trained-monkey.org>,
Paul Menzel <pmenzel@molgen.mpg.de>,
colyli@suse.de, linux-raid@vger.kernel.org
Cc: linfeilong <linfeilong@huawei.com>,
louhongxiang@huawei.com, lixiaokeng@huawei.com
Subject: Re: [Question] mdadm CVE-2023-28736 and CVE-2023-28938 problem
Date: Fri, 01 Sep 2023 10:04:55 +0200 [thread overview]
Message-ID: <c0cf475b190e7ab85061a9f462f4ea07587fa7eb.camel@suse.com> (raw)
In-Reply-To: <0837f65fca414498441d6f18904d89f9a09e1a9e.camel@suse.com>
On Thu, 2023-08-31 at 12:04 +0200, Martin Wilck wrote:
> On Thu, 2023-08-31 at 17:26 +0800, miaoguanqin wrote:
> > Dear mdadm committers:
> >
> > Hi! I noticed that the community did not provide the concrete patch
> > that could fix CVE-2023-28736 and CVE-2023-28938. Intel, in
> > specific,
> > suggests upgrading mdadm to version 4.2-rc2 or later [1], to get
> > rid
> > of
> > the issue, however, without finding the root cause or providing
> > further
> > explanation.I would like to know if there is such a specific patch,
> > or a set of patches that actually solve these two CVE problems.
> >
> > [1]
> > https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00690.html
> >
>
> I think it's ced5fa8 ("mdadm: block creation with long names").
... and the other was 7d374a1 ("Fix memory leak after "mdadm --
detail"")
Martin
prev parent reply other threads:[~2023-09-01 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 9:26 [Question] mdadm CVE-2023-28736 and CVE-2023-28938 problem miaoguanqin
2023-08-31 10:04 ` Martin Wilck
2023-09-01 8:04 ` Martin Wilck [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=c0cf475b190e7ab85061a9f462f4ea07587fa7eb.camel@suse.com \
--to=mwilck@suse.com \
--cc=colyli@suse.de \
--cc=jes@trained-monkey.org \
--cc=linfeilong@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=lixiaokeng@huawei.com \
--cc=louhongxiang@huawei.com \
--cc=miaoguanqin@huawei.com \
--cc=pmenzel@molgen.mpg.de \
/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;
as well as URLs for NNTP newsgroup(s).