All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Cc: Greg Kurz <groug@kaod.org>, Yanwu Shen <ywsPlz@gmail.com>,
	Jietao Xiao <shawtao1125@gmail.com>,
	Jinku Li <jkli@xidian.edu.cn>, Wenbo Shen <shenwenbo@zju.edu.cn>,
	Mauro Matteo Cascella <mcascell@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>
Subject: [PULL 0/1] 9p security fix 2023-06-08
Date: Thu, 08 Jun 2023 17:09:37 +0200	[thread overview]
Message-ID: <cover.1686236977.git.qemu_oss@crudebyte.com> (raw)

The following changes since commit 45ae97993a75f975f1a01d25564724c7e10a543f:

  Merge tag 'pull-tricore-20230607' of https://github.com/bkoppelmann/qemu into staging (2023-06-07 11:45:22 -0700)

are available in the Git repository at:

  https://github.com/cschoenebeck/qemu.git tags/pull-9p-20230608

for you to fetch changes up to f6b0de53fb87ddefed348a39284c8e2f28dc4eda:

  9pfs: prevent opening special files (CVE-2023-2861) (2023-06-08 17:04:58 +0200)

----------------------------------------------------------------
* Fix for CVE-2023-2861.

----------------------------------------------------------------
Christian Schoenebeck (1):
      9pfs: prevent opening special files (CVE-2023-2861)

 fsdev/virtfs-proxy-helper.c | 27 +++++++++++++++++++++++++--
 hw/9pfs/9p-util.h           | 39 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 64 insertions(+), 2 deletions(-)


             reply	other threads:[~2023-06-08 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 15:09 Christian Schoenebeck [this message]
2023-06-08 15:09 ` [PULL 1/1] 9pfs: prevent opening special files (CVE-2023-2861) Christian Schoenebeck
2023-06-08 20:31 ` [PULL 0/1] 9p security fix 2023-06-08 Richard Henderson

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=cover.1686236977.git.qemu_oss@crudebyte.com \
    --to=qemu_oss@crudebyte.com \
    --cc=groug@kaod.org \
    --cc=jkli@xidian.edu.cn \
    --cc=mcascell@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=shawtao1125@gmail.com \
    --cc=shenwenbo@zju.edu.cn \
    --cc=ywsPlz@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 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.