public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Frohl <rfrohl@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Red Hat Product Security <secalert@redhat.com>,
	security@suse.de, cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread()
Date: Wed, 6 Mar 2024 10:53:03 +0100	[thread overview]
Message-ID: <84949c3f-ed90-4c88-89d8-eab66025f8d3@suse.de> (raw)
In-Reply-To: <2024030635-alibi-obtrusive-133e@gregkh>


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



On 06.03.24 10:45, Greg KH wrote:
> On Wed, Mar 06, 2024 at 10:23:37AM +0100, Robert Frohl wrote:
>> On 06.03.24 10:16, Greg KH wrote:
>>> On Tue, Mar 05, 2024 at 10:30:08AM -0800, Red Hat Product Security wrote:
>>>>
>>>> Hello Robert,
>>>>    Thank you for reaching to Red Hat Product Security.
>>>>    I have reviewed the flaws, CVE-2023-1192 has the correct patch used in the reference.
>>>
>>> What do you mean by "reference"?
>>>
>>> CVE-2023-1192 points to a patch for a totally different filesystem
>>> (ntfs3).  Will that be fixed?
>>
>> This is also stated in the RH bugzilla, that the initial patch was wrong:
>> https://bugzilla.redhat.com/show_bug.cgi?id=2154178#c28
> 
> Ok, so what will RH be doing here?
> 
> confused,

I hope that the additional information will help to update the published 
information.

The bug states that the initial patch was wrong, but it looks like it 
just was never updated/fixed in the published information for CVE-2023-1192.

Cheers,
Robert

-- 
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-06  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 18:30 Re: CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread() 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 [this message]
     [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

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=84949c3f-ed90-4c88-89d8-eab66025f8d3@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