mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: Wang Zhaolong <wangzhaolong@huaweicloud.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2022-50455: nfs: fix possible null-ptr-deref when parsing param
Date: Fri, 10 Oct 2025 17:30:37 +0200	[thread overview]
Message-ID: <2025101056-coleslaw-underrate-ec0e@gregkh> (raw)
In-Reply-To: <54b0b560-493b-4f08-859c-8c1c41cf4c27@huaweicloud.com>

On Fri, Oct 10, 2025 at 10:19:40AM +0800, Wang Zhaolong wrote:
> 
> 
> 
> 
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> > 
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > nfs: fix possible null-ptr-deref when parsing param
> > 
> > According to commit "vfs: parse: deal with zero length string value",
> > kernel will set the param->string to null pointer in vfs_parse_fs_string()
> > if fs string has zero length.
> > 
> 
> Hi Greg,
> 
> The patch "vfs: parse: deal with zero length string value", which introduced
> this issue, was never merged into mainline.
> 
> It only exists in the mailing list:
> https://lists.openwall.net/linux-kernel/2022/06/28/18

Please always use lore.kernel.org for emails, I had to go dig out the
whole thread from there based on that to determine what happened here :(

> Since the problematic behavior never existed in any released kernel,
> CVE-2022-50455 cannot be valid.
> 
> Please consider rejecting this CVE.

Makes sense, I'll go reject this now, thanks for the review!

greg k-h

      reply	other threads:[~2025-10-10 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025100118-CVE-2022-50455-24fb@gregkh>
2025-10-10  2:19 ` Wang Zhaolong
2025-10-10 15:30   ` Greg Kroah-Hartman [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=2025101056-coleslaw-underrate-ec0e@gregkh \
    --to=gregkh@kernel.org \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangzhaolong@huaweicloud.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®