From: Auger Eric <eric.auger@redhat.com>
To: Kees Cook <keescook@chromium.org>,
Christoffer Dall <christoffer.dall@arm.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM: arm64: vgic-its: Remove VLA usage
Date: Mon, 2 Jul 2018 09:36:44 +0200 [thread overview]
Message-ID: <19f9ddb1-6009-850c-1949-3a8cdacdd2fc@redhat.com> (raw)
In-Reply-To: <20180629184618.GA37364@beast>
Hi Kees,
On 06/29/2018 08:46 PM, Kees Cook wrote:
> In the quest to remove all stack VLA usage from the kernel[1], this
> switches to using a maximum size and adds sanity checks. Additionally
> cleans up some of the int-vs-u32 usage and adds additional bounds checking.
> As it currently stands, this will always be 8 bytes until the ABI changes.
>
> [1] https://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qPXydAacU1RqZWA@mail.gmail.com
>
> Cc: Christoffer Dall <christoffer.dall@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Eric Auger <eric.auger@redhat.com>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: kvmarm@lists.cs.columbia.edu
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> virt/kvm/arm/vgic/vgic-its.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
> index 4ed79c939fb4..3143fc047fcf 100644
> --- a/virt/kvm/arm/vgic/vgic-its.c
> +++ b/virt/kvm/arm/vgic/vgic-its.c
> @@ -168,8 +168,14 @@ struct vgic_its_abi {
> int (*commit)(struct vgic_its *its);
> };
>
> +#define ABI_0_ESZ 8
> +#define ESZ_MAX ABI_0_ESZ
> +
> static const struct vgic_its_abi its_table_abi_versions[] = {
> - [0] = {.cte_esz = 8, .dte_esz = 8, .ite_esz = 8,
> + [0] = {
> + .cte_esz = ABI_0_ESZ,
> + .dte_esz = ABI_0_ESZ,
> + .ite_esz = ABI_0_ESZ,
> .save_tables = vgic_its_save_tables_v0,
> .restore_tables = vgic_its_restore_tables_v0,
> .commit = vgic_its_commit_v0,
> @@ -180,10 +186,12 @@ static const struct vgic_its_abi its_table_abi_versions[] = {
>
> inline const struct vgic_its_abi *vgic_its_get_abi(struct vgic_its *its)
> {
> + if (WARN_ON(its->abi_rev >= NR_ITS_ABIS))
> + return NULL;
> return &its_table_abi_versions[its->abi_rev];
> }
>
> -int vgic_its_set_abi(struct vgic_its *its, int rev)
> +static int vgic_its_set_abi(struct vgic_its *its, u32 rev)
> {
if vgic_its_get_abi is likely to return NULL, don't we need to check abi
!= NULL in all call sites.
abi_rev is actually set by vgic_its_set_abi() which is actually called
by vgic_mmio_uaccess_write_its_iidr() and vgic_its_create().
Only vgic_mmio_uaccess_write_its_iidr allows the userspace to overwrite
the default abi_rev. At this point a check against NR_ITS_ABIS is
already done. So to me the check is done at the source?
Thanks
Eric
> const struct vgic_its_abi *abi;
>
> @@ -1881,16 +1889,19 @@ typedef int (*entry_fn_t)(struct vgic_its *its, u32 id, void *entry,
> * Return: < 0 on error, 0 if last element was identified, 1 otherwise
> * (the last element may not be found on second level tables)
> */
> -static int scan_its_table(struct vgic_its *its, gpa_t base, int size, int esz,
> +static int scan_its_table(struct vgic_its *its, gpa_t base, int size, u32 esz,
> int start_id, entry_fn_t fn, void *opaque)
> {
> struct kvm *kvm = its->dev->kvm;
> unsigned long len = size;
> int id = start_id;
> gpa_t gpa = base;
> - char entry[esz];
> + char entry[ESZ_MAX];
> int ret;
>
> + if (WARN_ON(esz > ESZ_MAX))
> + return -EINVAL;
> +
> memset(entry, 0, esz);
>
> while (len > 0) {
>
next prev parent reply other threads:[~2018-07-02 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 18:46 Kees Cook
2018-06-29 21:25 ` Arnd Bergmann
2018-07-02 7:36 ` Auger Eric [this message]
2018-07-02 17:15 ` Kees Cook
2018-07-09 10:47 ` Marc Zyngier
2018-07-09 15:53 ` Kees Cook
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=19f9ddb1-6009-850c-1949-3a8cdacdd2fc@redhat.com \
--to=eric.auger@redhat.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@arm.com \
--cc=keescook@chromium.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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®