From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl
Date: Thu, 12 Sep 2019 12:47:13 +0200 [thread overview]
Message-ID: <4ed0c815-c598-bb0f-9841-d579fc62877f@de.ibm.com> (raw)
In-Reply-To: <20190912090050.20295-1-thuth@redhat.com>
On 12.09.19 11:00, Thomas Huth wrote:
> When the userspace program runs the KVM_S390_INTERRUPT ioctl to inject
> an interrupt, we convert them from the legacy struct kvm_s390_interrupt
> to the new struct kvm_s390_irq via the s390int_to_s390irq() function.
> However, this function does not take care of all types of interrupts
> that we can inject into the guest later (see do_inject_vcpu()). Since we
> do not clear out the s390irq values before calling s390int_to_s390irq(),
> there is a chance that we copy unwanted data from the kernel stack
> into the guest memory later if the interrupt data has not been properly
> initialized by s390int_to_s390irq().
You mean by using the migration callbacks to get all interrupts back to
userspace?
>
> Specifically, the problem exists with the KVM_S390_INT_PFAULT_INIT
> interrupt: s390int_to_s390irq() does not handle it, but the function
> __deliver_pfault_init() will later copy the uninitialized stack data
> from the ext.ext_params2 into the guest memory.
Shouldnt we add some more detailed description how this can happen?
Something like
"By using the KVM_S390_INTERRUPT ioctl with a KVM_S390_INT_PFAULT_INIT
interrupt followed by the KVM_S390_GET_IRQ_STATE ioctl the user can
extract a value from the kernel stack."
>
> Fix it by handling that interrupt type in s390int_to_s390irq(), too.
> And while we're at it, make sure that s390int_to_s390irq() now
> directly returns -EINVAL for unknown interrupt types, so that we
> do not run into this problem again in case we add more interrupt
> types to do_inject_vcpu() sometime in the future.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Cc: stable
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> arch/s390/kvm/interrupt.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index 3e7efdd9228a..165dea4c7f19 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -1960,6 +1960,16 @@ int s390int_to_s390irq(struct kvm_s390_interrupt *s390int,
> case KVM_S390_MCHK:
> irq->u.mchk.mcic = s390int->parm64;
> break;
> + case KVM_S390_INT_PFAULT_INIT:
> + irq->u.ext.ext_params = s390int->parm;
> + irq->u.ext.ext_params2 = s390int->parm64;
> + break;
> + case KVM_S390_RESTART:
> + case KVM_S390_INT_CLOCK_COMP:
> + case KVM_S390_INT_CPU_TIMER:
> + break;
> + default:
> + return -EINVAL;
> }
> return 0;
> }
>
next prev parent reply other threads:[~2019-09-12 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 9:00 [PATCH] KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl Thomas Huth
2019-09-12 9:14 ` David Hildenbrand
2019-09-12 9:20 ` Thomas Huth
2019-09-12 9:28 ` Janosch Frank
2019-09-12 10:52 ` Christian Borntraeger
2019-09-12 11:23 ` Thomas Huth
2019-09-13 7:20 ` Cornelia Huck
2019-09-13 7:34 ` Thomas Huth
2019-09-13 7:37 ` David Hildenbrand
2019-09-13 7:43 ` Thomas Huth
2019-09-13 7:47 ` David Hildenbrand
2019-09-12 10:58 ` David Hildenbrand
2019-09-12 11:00 ` Christian Borntraeger
2019-09-12 10:47 ` Christian Borntraeger [this message]
2019-09-12 11:08 ` Thomas Huth
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=4ed0c815-c598-bb0f-9841-d579fc62877f@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@redhat.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