All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, Feifan Qian <bea1e@proton.me>
Subject: Re: [PATCH 0/3] 9pfs: fix illegal names with Twstat rename
Date: Mon, 15 Jun 2026 11:04:50 +0200	[thread overview]
Message-ID: <2835535.mvXUDI8C0e@weasel> (raw)
In-Reply-To: <cover.1780072238.git.qemu_oss@crudebyte.com>

On Friday, 29 May 2026 18:30:38 CEST Christian Schoenebeck wrote:
> This series fixes a guest-triggerable assertion fault (DoS) caused by
> sending an illegal new name with the legacy Twstat rename handler.
> 
>  - Patch 1: This is the core fix that prevents the DoS vulnerability.
> 
>  - Patch 2: Additionally rejects "." and ".." as new names with Twstat
>    rename operations (not being a vulnerability though).
> 
>  - Patch 3: Consolidates the name validation logic spread multiple
>    times over multiple request handlers.
> 
> Christian Schoenebeck (3):
>   hw/9pfs: fix abort due to illegal name with Twstat rename
>   hw/9pfs: reject . and .. in Twstat rename
>   hw/9pfs: consolidate name validation with check_name()
> 
>  hw/9pfs/9p.c | 97 +++++++++++++++++++++++-----------------------------
>  1 file changed, 42 insertions(+), 55 deletions(-)

Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next

Thanks!

/Christian




      parent reply	other threads:[~2026-06-15  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 16:30 [PATCH 0/3] 9pfs: fix illegal names with Twstat rename Christian Schoenebeck
2026-05-29 16:29 ` [PATCH 1/3] hw/9pfs: fix abort due to illegal name " Christian Schoenebeck
2026-05-29 16:29 ` [PATCH 2/3] hw/9pfs: reject . and .. in " Christian Schoenebeck
2026-05-29 16:29 ` [PATCH 3/3] hw/9pfs: consolidate name validation with check_name() Christian Schoenebeck
2026-06-15  9:04 ` Christian Schoenebeck [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=2835535.mvXUDI8C0e@weasel \
    --to=qemu_oss@crudebyte.com \
    --cc=bea1e@proton.me \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    /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.