From: Greg KH <gregkh@linuxfoundation.org>
To: Robert Frohl <rfrohl@suse.de>
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 09:45:33 +0000 [thread overview]
Message-ID: <2024030635-alibi-obtrusive-133e@gregkh> (raw)
In-Reply-To: <265fb3da-8961-4f4f-8f81-c271e5aceebc@suse.de>
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,
greg k-h
next prev parent reply other threads:[~2024-03-06 9:45 UTC|newest]
Thread overview: 9+ 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 [this message]
2024-03-06 9:53 ` Robert Frohl
-- strict thread matches above, loose matches on Subject: below --
2024-03-02 22:00 Greg Kroah-Hartman
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=2024030635-alibi-obtrusive-133e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rfrohl@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.