From: sashiko-bot@kernel.org
To: "Eric Farman" <farman@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
kvm@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>
Subject: Re: [PATCH v5 05/10] s390/vfio_ccw: calculate idal length based on idaw type
Date: Sun, 26 Jul 2026 04:14:47 +0000 [thread overview]
Message-ID: <20260726041447.DD1961F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260726040129.2946151-6-farman@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Guest IOVAs are passed untranslated to the host channel subsystem for skipped I/O operations, allowing physical memory probing.
--
--- Patch [5]: [PATCH v5 05/10] s390/vfio_ccw: calculate idal length based on idaw type ---
commit 8013df87ffdce265ecd327b26da1e700483c050d
Author: Eric Farman <farman@linux.ibm.com>
Subject: s390/vfio_ccw: calculate idal length based on idaw type
The patch fixes the length calculation of IDAL in get_guest_idal() so it
doesn't unconditionally assume Format-2 IDAW sizes. Input IDALs can be
Format-1 (31-bit) or Format-2 (64-bit), requiring dynamic size calculation.
Link: https://lore.kernel.org/r/20260720203400.7328E1F000E9@smtp.kernel.org/
> diff --git a/drivers/s390/cio/vfio_ccw_cp.c b/drivers/s390/cio/vfio_ccw_cp.c
> index 6275794751cb4..5ef082b8289af 100644
> --- a/drivers/s390/cio/vfio_ccw_cp.c
> +++ b/drivers/s390/cio/vfio_ccw_cp.c
[ ... ]
> @@ -524,7 +525,7 @@ static dma64_t *get_guest_idal(struct ccw1 *ccw, struct channel_program *cp, int
> dma64_t *idaws;
> dma32_t *idaws_f1;
> u64 first_idaw;
> - int idal_len = idaw_nr * sizeof(*idaws);
> + int idal_len = idaw_nr * get_idaw_size(cp);
[Severity: High]
This is a pre-existing issue, but I have a question about how we handle
skipped I/O operations. Is it possible for untranslated guest IOVAs to
be leaked to the host hardware if the CCW has the SKIP flag set or if
count is 0?
When get_guest_idal() populates the idaws array, it copies the IDAL
directly from the guest. Later, if ccw_does_data_transfer() returns
false, ccwchain_fetch_ccw() skips pinning and sets pa->pa_nr = 0:
drivers/s390/cio/vfio_ccw_cp.c:ccwchain_fetch_ccw() {
...
if (ccw_does_data_transfer(ccw)) {
ret = page_array_pin(pa, vdev, idal_is_2k(cp));
if (ret < 0)
goto out_unpin;
} else {
pa->pa_nr = 0;
}
...
}
This then causes page_array_idal_create_words() to perform zero iterations
because its loop is bounded by pa->pa_nr:
drivers/s390/cio/vfio_ccw_cp.c:page_array_idal_create_words() {
...
for (i = 0; i < pa->pa_nr; i++) {
idaws[i] = virt_to_dma64(page_to_virt(pa->pa_page[i]));
}
...
}
Would this result in the guest IOVAs remaining in the idaws array,
leaving the untranslated guest addresses exposed to the host hardware?
Since the hardware still validates physical addresses even for skipped
operations, could a malicious guest use this to probe host physical
memory and bypass KASLR?
> int idaw_size = idal_is_2k(cp) ? PAGE_SIZE / 2 : PAGE_SIZE;
> int idaw_mask = ~(idaw_size - 1);
> int i, ret;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260726040129.2946151-1-farman@linux.ibm.com?part=5
next prev parent reply other threads:[~2026-07-26 4:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 4:01 [PATCH v5 00/10] s390/vfio_ccw fixes Eric Farman
2026-07-26 4:01 ` [PATCH v5 01/10] s390/vfio_ccw: free all memory if cp_init() fails Eric Farman
2026-07-26 4:15 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 02/10] s390/vfio_ccw: limit the number of channel program segments Eric Farman
2026-07-26 4:08 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 03/10] s390/vfio_ccw: fix out of bounds check on CCW array Eric Farman
2026-07-26 4:33 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 04/10] s390/vfio_ccw: ensure first IDAW remains constant Eric Farman
2026-07-26 4:18 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 05/10] s390/vfio_ccw: calculate idal length based on idaw type Eric Farman
2026-07-26 4:14 ` sashiko-bot [this message]
2026-07-26 4:01 ` [PATCH v5 06/10] s390/vfio_ccw: ensure index for read/write regions are within range Eric Farman
2026-07-26 4:16 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 07/10] s390/vfio_ccw: cancel existing workqueues Eric Farman
2026-07-26 4:16 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 08/10] s390/vfio_ccw: move cp cleanup out of not operational Eric Farman
2026-07-26 4:14 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 09/10] s390/vfio_ccw: implement a channel program mutex Eric Farman
2026-07-26 4:18 ` sashiko-bot
2026-07-26 4:01 ` [PATCH v5 10/10] s390/vfio_ccw: implement a crw lock Eric Farman
2026-07-26 4:27 ` 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=20260726041447.DD1961F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--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