mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Frohl <rfrohl@suse.de>
To: Red Hat Product Security <secalert@redhat.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"security@suse.de" <security@suse.de>
Subject: Re: CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread()
Date: Tue, 5 Mar 2024 13:12:43 +0100	[thread overview]
Message-ID: <2323c190-ed11-4723-bf96-4949c55c7ffa@suse.de> (raw)
In-Reply-To: <2024030513-unburned-eggplant-a218@gregkh>


[-- Attachment #1.1.1: Type: text/plain, Size: 1499 bytes --]

Hi Redhat Security,

could you have a look and update the entry for CVE-2023-1192, if you 
agree that CVE-2023-52572 is a duplicate and the referenced patch for 
CVE-2023-1192 is incorrect ?

Thanks,
Robert

On 05.03.24 12:08, Greg Kroah-Hartman wrote:
> 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

-- 
Security Engineer, SUSE Software Solutions Germany GmbH, Frankenstraße 
146, 90461 Nürnberg, Germany, GF: Ivo Totev, Andrew McDonald, Werner 
Knoblich (HRB 36809, AG Nürnberg)
GPG: D29F 82AA 9FD5 9D6E 74B1  6370 089E DB3D 230A 2404

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 12035 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-03-05 12:12 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 ` Robert Frohl
2024-03-05 11:08   ` Greg Kroah-Hartman
2024-03-05 12:12     ` Robert Frohl [this message]
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=2323c190-ed11-4723-bf96-4949c55c7ffa@suse.de \
    --to=rfrohl@suse.de \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=secalert@redhat.com \
    --cc=security@suse.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

all inboxes | Powered by JetHome®