From: Ben Hutchings <benh@debian.org>
To: Paulo Alcantara <pc@manguebit.com>,
Salvatore Bonaccorso <carnil@debian.org>,
Steve French <sfrench@samba.org>,
Ronnie Sahlberg <lsahlber@redhat.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>
Cc: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org
Subject: Re: Information on use-after-free in smb2_is_status_io_timeout()?
Date: Fri, 05 Jan 2024 19:14:57 +0100 [thread overview]
Message-ID: <aca1c4e755e8c005b874c57a6210c4c6a34d2324.camel@debian.org> (raw)
In-Reply-To: <1d2bb04665d19a4722a0b9f7f552cab3@manguebit.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Fri, 2024-01-05 at 11:04 -0300, Paulo Alcantara wrote:
> Salvatore Bonaccorso <carnil@debian.org> writes:
>
> > There is a Red Hat bugzilla report in
> > https://bugzilla.redhat.com/show_bug.cgi?id=2154178 about a
> > use-after-free in smb2_is_status_io_timeout() . While the commit noted
> > initially there seems not correct, Ben Hutchings raised a question on
> > more information in
> > https://bugzilla.redhat.com/show_bug.cgi?id=2154178#c24 .
> >
> > (there is a CVE assigned for it, CVE-2023-1192)
>
> That is supposed to be fixed by
>
> d527f51331ca ("cifs: Fix UAF in cifs_demultiplex_thread()")
>
> While the commit refers to an UAF in ->is_network_name_deleted(), this
> should also work for smb2_is_status_io_timeout(), AFAICT.
I think that's a different UAF bug that happens to affect the same
function.
Ben.
--
Ben Hutchings - Debian developer, member of kernel, installer and LTS
teams
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-05 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 13:33 Salvatore Bonaccorso
2024-01-05 14:04 ` Paulo Alcantara
2024-01-05 18:14 ` Ben Hutchings [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=aca1c4e755e8c005b874c57a6210c4c6a34d2324.camel@debian.org \
--to=benh@debian.org \
--cc=carnil@debian.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.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®