All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org, nobuhiro1.iwamatsu@toshiba.co.jp,
	masami.ichikawa@miraclelinux.com, Chris.Paterson2@renesas.com
Subject: Disabling XEN in our configs (used by QEMU and Renesas)
Date: Thu, 17 Mar 2022 10:58:03 +0100	[thread overview]
Message-ID: <20220317095803.GA2237@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Hi!

There is bunch of XEN security fixes in the pipeline:

CVE-2022-23036, CVE-2022-23037, CVE-2022-23038, CVE-2022-23039,
CVE-2022-23040 : Xen: fix race conditions, resulting in potential data
leaks, data corruption, DoS by malicious backends

CVE-2022-23041: Xen: fix race conditions, resulting in potential data
leaks, data corruption, DoS by malicious backends

CVE-2022-23042: Xen: fix race conditions, resulting in potential data
leaks, data corruption, DoS by malicious backends

There's a bunch of patches fixing those, but backporting them to 4.4
would not be exactly easy. Our scripts show XEN as being used, but I
suspect that's a mistake.

Reneasas, can you confirm if you are using XEN in your arm64 products?
If not, it would be good to disable it in the configs.

Could we disable XEN in qemu configs? I don't believe it makes much
sense.

./4.19.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN=y
./4.19.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN_GNTDEV=y
./4.19.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN_GRANT_DEV_ALLOC=y
./4.19.y-cip/arm64/renesas_defconfig:CONFIG_XEN=y
./5.10.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN=y
./5.10.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN_GNTDEV=y
./5.10.y-cip/arm64/qemu_arm64_defconfig:CONFIG_XEN_GRANT_DEV_ALLOC=y
./5.10.y-cip/arm64/renesas_defconfig:CONFIG_XEN=y
./4.19.y-cip-rt/arm64/renesas-rt_defconfig:CONFIG_XEN=y
./5.10.y-cip-rt/arm64/renesas-rt_defconfig:CONFIG_XEN=y

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2022-03-17  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  9:58 Pavel Machek [this message]
2022-03-17 10:30 ` Disabling XEN in our configs (used by QEMU and Renesas) Chris Paterson

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=20220317095803.GA2237@amd \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=masami.ichikawa@miraclelinux.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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.