From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robert Frohl <rfrohl@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread()
Date: Tue, 5 Mar 2024 11:08:09 +0000 [thread overview]
Message-ID: <2024030513-unburned-eggplant-a218@gregkh> (raw)
In-Reply-To: <ae3d431d-d93f-4fe4-99c9-7157bebaff79@suse.com>
On Tue, Mar 05, 2024 at 11:38:49AM +0100, Robert Frohl wrote:
> Hi all,
>
> this seems to be a duplicate of CVE-2023-1192 [0], even though NVD lists
> another, wrong patch. The RH bug has more details [1].
>
> Cheers,
> Robert
>
>
> [0] https://nvd.nist.gov/vuln/detail/CVE-2023-1192
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2154178#c28
That's a mess. Please have RH update the json entry with CVE with the
correct git commit id and then I'll be glad to revoke this. The
information in NVD is not "real" from the point of view of the CVE
database, so I can't take information there as being correct, or not.
As you know, NVD is just an add-on for CVE entries, one of many created
by many different groups/governments.
Until it's fixed in the CVE database, this CVE should stand as it refers
to the correct fix that people need to know about, not the incorrect one
in the RH-assigned CVE.
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-05 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024030256-CVE-2023-52572-2b92@gregkh>
2024-03-05 10:38 ` CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread() Robert Frohl
2024-03-05 11:08 ` Greg Kroah-Hartman [this message]
2024-03-05 12:12 ` Robert Frohl
2024-03-05 18:30 Red Hat Product Security
2024-03-06 9:16 ` Greg KH
2024-03-06 9:23 ` Robert Frohl
2024-03-06 9:45 ` Greg KH
2024-03-06 9:53 ` Robert Frohl
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=2024030513-unburned-eggplant-a218@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rfrohl@suse.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