From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, Akihiro Suda <suda.kyoto@gmail.com>,
jan.dubois@suse.com, anders.f.bjorklund@gmail.com,
qemu-stable@nongnu.org,
Balaji Vijayakumar <kuttibalaji.v6@gmail.com>
Subject: Re: [PATCH] 9pfs: fix crash on 'Treaddir' request
Date: Tue, 05 Nov 2024 17:15:37 +0100 [thread overview]
Message-ID: <1897217.tevHOsptmc@silver> (raw)
In-Reply-To: <20241105123803.0923c22e@bahia>
On Tuesday, November 5, 2024 1:13:14 PM CET Greg Kurz wrote:
> On Tue, 5 Nov 2024 11:25:26 +0100
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
>
> > A bad (broken or malicious) 9p client (guest) could cause QEMU host to
> > crash by sending a 9p 'Treaddir' request with a numeric file ID (FID) that
> > was previously opened for a file instead of an expected directory:
> >
> > #0 0x0000762aff8f4919 in __GI___rewinddir (dirp=0xf) at
> > ../sysdeps/unix/sysv/linux/rewinddir.c:29
> > #1 0x0000557b7625fb40 in do_readdir_many (pdu=0x557bb67d2eb0,
> > fidp=0x557bb67955b0, entries=0x762afe9fff58, offset=0, maxsize=131072,
> > dostat=<optimized out>) at ../hw/9pfs/codir.c:101
> > #2 v9fs_co_readdir_many (pdu=pdu@entry=0x557bb67d2eb0,
> > fidp=fidp@entry=0x557bb67955b0, entries=entries@entry=0x762afe9fff58,
> > offset=0, maxsize=131072, dostat=false) at ../hw/9pfs/codir.c:226
> > #3 0x0000557b7625c1f9 in v9fs_do_readdir (pdu=0x557bb67d2eb0,
> > fidp=0x557bb67955b0, offset=<optimized out>,
> > max_count=<optimized out>) at ../hw/9pfs/9p.c:2488
> > #4 v9fs_readdir (opaque=0x557bb67d2eb0) at ../hw/9pfs/9p.c:2602
> >
> > That's because V9fsFidOpenState was declared as union type. So the
> > same memory region is used for either an open POSIX file handle (int),
> > or a POSIX DIR* pointer, etc., so 9p server incorrectly used the
> > previously opened (valid) POSIX file handle (0xf) as DIR* pointer,
> > eventually causing a crash in glibc's rewinddir() function.
> >
> > Root cause was therefore a missing check in 9p server's 'Treaddir'
> > request handler, which must ensure that the client supplied FID was
> > really opened as directory stream before trying to access the
> > aforementioned union and its DIR* member.
> >
> > Cc: qemu-stable@nongnu.org
> > Fixes: d62dbb51f7 ("virtio-9p: Add fidtype so that we can do type ...")
> > Reported-by: Akihiro Suda <suda.kyoto@gmail.com>
> > Tested-by: Akihiro Suda <suda.kyoto@gmail.com>
> > Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> > ---
> > hw/9pfs/9p.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
>
> Wow ! And this is there since pretty much always... I'm amazed how
> it went unnoticed for so long :-)
Yeah, a true hero, lasted for amazing 14 years. :)
Probably a good wake-up call for looking into that fuzzing environment
somebody made for 9pfs. I never tried it myself.
> Reviewed-by: Greg Kurz <groug@kaod.org>
Thanks!
/Christian
next prev parent reply other threads:[~2024-11-05 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 10:25 [PATCH] 9pfs: fix crash on 'Treaddir' request Christian Schoenebeck via
2024-11-05 12:13 ` Greg Kurz
2024-11-05 16:15 ` Christian Schoenebeck [this message]
2024-11-07 14:22 ` Christian Schoenebeck
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=1897217.tevHOsptmc@silver \
--to=qemu_oss@crudebyte.com \
--cc=anders.f.bjorklund@gmail.com \
--cc=groug@kaod.org \
--cc=jan.dubois@suse.com \
--cc=kuttibalaji.v6@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=suda.kyoto@gmail.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;
as well as URLs for NNTP newsgroup(s).