From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Dmitry Frolov <frolov@swemel.ru>,
jonathan.cameron@huawei.com, fan.ni@samsung.com,
qemu-devel@nongnu.org
Cc: sdl.qemu@linuxtesting.org
Subject: Re: [PATCH] hw/cxl: Fix out of bound array access
Date: Wed, 13 Sep 2023 13:36:46 +0200 [thread overview]
Message-ID: <057bee7c-92e0-1cf2-bcdd-ef7eeb223db4@linaro.org> (raw)
In-Reply-To: <20230913101055.754709-1-frolov@swemel.ru>
Hi Dmitry,
On 13/9/23 12:10, Dmitry Frolov wrote:
> According to cxl_interleave_ways_enc(),
> fw->num_targets is allowed to be up to 16.
> This also corresponds to CXL specs.
> So, the fw->target_hbs[] array is iterated from 0 to 15.
> But it is staticaly declared of length 8.
"statically"
> Thus, out of bound array access may occur.
>
> Fixes: c28db9e000 ("hw/pci-bridge: Make PCIe and CXL PXB Devices inherit from TYPE_PXB_DEV")
>
> Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
> ---
> include/hw/cxl/cxl.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/hw/cxl/cxl.h b/include/hw/cxl/cxl.h
> index 56c9e7676e..4944725849 100644
> --- a/include/hw/cxl/cxl.h
> +++ b/include/hw/cxl/cxl.h
> @@ -29,7 +29,7 @@ typedef struct PXBCXLDev PXBCXLDev;
> typedef struct CXLFixedWindow {
> uint64_t size;
> char **targets;
> - PXBCXLDev *target_hbs[8];
> + PXBCXLDev *target_hbs[16];
> uint8_t num_targets;
> uint8_t enc_int_ways;
> uint8_t enc_int_gran;
The loop in cxl_fixed_memory_window_config() is indeed unsafe.
OOB can be catched adding:
-- >8 --
diff --git a/hw/cxl/cxl-host.c b/hw/cxl/cxl-host.c
index 034c7805b3..fe9143409b 100644
--- a/hw/cxl/cxl-host.c
+++ b/hw/cxl/cxl-host.c
@@ -33,6 +33,7 @@ static void cxl_fixed_memory_window_config(CXLState
*cxl_state,
for (target = object->targets; target; target = target->next) {
fw->num_targets++;
}
+ assert(fw->num_targets <= ARRAY_SIZE(fw->target_hbs));
fw->enc_int_ways = cxl_interleave_ways_enc(fw->num_targets, errp);
if (*errp) {
---
If Jonathan concurs, please add to your patch.
Thanks,
Phil.
next prev parent reply other threads:[~2023-09-13 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 10:10 [PATCH] hw/cxl: Fix out of bound array access Dmitry Frolov
2023-09-13 11:02 ` Jonathan Cameron via
2023-09-13 11:36 ` Philippe Mathieu-Daudé [this message]
2023-09-13 13:22 ` [PATCH v2] " Dmitry Frolov
2023-09-13 16:58 ` Jonathan Cameron via
2023-09-13 16:56 ` [PATCH] " Jonathan Cameron via
2023-09-14 7:06 ` [PATCH v3] " Dmitry Frolov
2023-09-14 12:36 ` Michael Tokarev
2023-09-14 12:37 ` [PATCH] " Michael Tokarev
2023-09-14 12:38 ` Michael Tokarev
2023-09-14 12:59 ` Philippe Mathieu-Daudé
2023-09-14 13:16 ` Michael Tokarev
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=057bee7c-92e0-1cf2-bcdd-ef7eeb223db4@linaro.org \
--to=philmd@linaro.org \
--cc=fan.ni@samsung.com \
--cc=frolov@swemel.ru \
--cc=jonathan.cameron@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=sdl.qemu@linuxtesting.org \
/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;
as well as URLs for NNTP newsgroup(s).