From: sashiko-bot@kernel.org
To: "Heiko Carstens" <hca@linux.ibm.com>
Cc: "Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v4 2/4] KVM: s390: Remove cond_resched() calls
Date: Fri, 31 Jul 2026 17:05:39 +0000 [thread overview]
Message-ID: <20260731170540.3CBCC1F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260731165004.2758105-3-hca@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Missing bounds check on `user_data_len` allows an out-of-bounds read of kernel memory by the Ultravisor.
--
--- Patch [2]: [PATCH v4 2/4] KVM: s390: Remove cond_resched() calls ---
commit 6586b58419c33753e59827884fdaa5a7f473b641
Author: Heiko Carstens <hca@linux.ibm.com>
KVM: s390: Remove cond_resched() calls
Since [1] cond_resched() is a no-op on s390. Remove all calls.
This also entirely removes uv_call_sched() and replaces all call sites
with uv_call(), since both functions are identical after the removal
of cond_resched().
[1] commit 7dadeaa6e851 ("sched: Further restrict the preemption modes")
> diff --git a/drivers/s390/char/uvdevice.c b/drivers/s390/char/uvdevice.c
> index e6a264c996ce3..4d274a2ee84dd 100644
> --- a/drivers/s390/char/uvdevice.c
> +++ b/drivers/s390/char/uvdevice.c
[ ... ]
> @@ -224,7 +224,7 @@ static int uvio_attestation(struct uvio_ioctl_cb *uv_ioctl)
> if (ret)
> goto out;
>
> - uv_call_sched(0, (u64)uvcb_attest);
> + uv_call(0, (u64)uvcb_attest);
[Severity: High]
This is a pre-existing issue, but does get_uvio_attest() validate the size of
user_data_len?
Looking at uvio_attestation(), it calls get_uvio_attest() to populate
uvio_attest, but there appears to be no bounds check on
uvio_attest->user_data_len. Then in uvio_build_uvcb_attest(), this unvalidated
length is copied to uvcb_attest->user_data_len before making this Ultravisor
call.
Since uvcb_attest is allocated in kernel memory, could a malicious user
provide a large user_data_len (up to 65535) and cause the Ultravisor firmware
to read beyond the bounds of the uvcb_attest allocation? This might lead to a
system crash if it accesses unmapped physical memory, or it could leak
adjacent kernel heap contents by incorporating them into the cryptographic
measurement returned to the user.
>
> uv_ioctl->uv_rc = uvcb_attest->header.rc;
> uv_ioctl->uv_rrc = uvcb_attest->header.rrc;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260731165004.2758105-1-hca@linux.ibm.com?part=2
next prev parent reply other threads:[~2026-07-31 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 16:50 [PATCH v4 0/4] s390: Remove or replace cond_resched() calls Heiko Carstens
2026-07-31 16:50 ` [PATCH v4 1/4] s390/crypto: Replace cond_resched() with msleep(1) Heiko Carstens
2026-07-31 17:06 ` sashiko-bot
2026-07-31 18:31 ` Holger Dengler
2026-07-31 16:50 ` [PATCH v4 2/4] KVM: s390: Remove cond_resched() calls Heiko Carstens
2026-07-31 17:05 ` sashiko-bot [this message]
2026-07-31 16:50 ` [PATCH v4 3/4] " Heiko Carstens
2026-07-31 16:53 ` sashiko-bot
2026-07-31 16:50 ` [PATCH v4 4/4] s390/cio: " Heiko Carstens
2026-07-31 16:59 ` sashiko-bot
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=20260731170540.3CBCC1F00AC4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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