From: Fan Ni <nifan.cxl@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-cxl@vger.kernel.org, mst@redhat.com, qemu-devel@nongnu.org,
Esifiel <esifiel@gmail.com>,
linuxarm@huawei.com
Subject: Re: [PATCH qemu 03/10] hw/cxl: Check input length is large enough in cmd_events_clear_records()
Date: Tue, 5 Nov 2024 13:01:30 -0800 [thread overview]
Message-ID: <ZyqHqsFQzjDaEP8w@fan> (raw)
In-Reply-To: <20241101133917.27634-4-Jonathan.Cameron@huawei.com>
On Fri, Nov 01, 2024 at 01:39:10PM +0000, Jonathan Cameron wrote:
> Buggy software might write a message that is too short for
> either the header, or the header + the event data that is specified
> in the header. This may result in accesses beyond the range of the
> message allocated as a duplicate of the incoming message buffer.
>
> Reported-by: Esifiel <esifiel@gmail.com>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
Reviewed-by: Fan Ni <fan.ni@samsung.com>
> hw/cxl/cxl-mailbox-utils.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/cxl/cxl-mailbox-utils.c b/hw/cxl/cxl-mailbox-utils.c
> index e63140aefe..3cb499a24f 100644
> --- a/hw/cxl/cxl-mailbox-utils.c
> +++ b/hw/cxl/cxl-mailbox-utils.c
> @@ -266,6 +266,12 @@ static CXLRetCode cmd_events_clear_records(const struct cxl_cmd *cmd,
> CXLClearEventPayload *pl;
>
> pl = (CXLClearEventPayload *)payload_in;
> +
> + if (len_in < sizeof(*pl) ||
> + len_in < sizeof(*pl) + sizeof(*pl->handle) * pl->nr_recs) {
> + return CXL_MBOX_INVALID_PAYLOAD_LENGTH;
> + }
> +
> *len_out = 0;
> return cxl_event_clear_records(cxlds, pl);
> }
> --
> 2.43.0
>
--
Fan Ni
next prev parent reply other threads:[~2024-11-05 21:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:39 [PATCH qemu 00/10] hw/cxl: Mailbox input parser hardening against invalid input Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-01 13:39 ` [PATCH qemu 01/10] hw/cxl: Check size of input data to dynamic capacity mailbox commands Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 18:01 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 02/10] hw/cxl: Check input includes at least the header in cmd_features_set_feature() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 20:59 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 03/10] hw/cxl: Check input length is large enough in cmd_events_clear_records() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:01 ` Fan Ni [this message]
2024-11-01 13:39 ` [PATCH qemu 04/10] hw/cxl: Check enough data in cmd_firmware_update_transfer() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:04 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 05/10] hw/cxl: Check the length of data requested fits in get_log() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:12 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 06/10] hw/cxl: Avoid accesses beyond the end of cel_log Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:18 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 07/10] hw/cxl: Ensuring enough data to read parameters in cmd_tunnel_management_cmd() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:20 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 08/10] hw/cxl: Check that writes do not go beyond end of target attributes Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:32 ` Fan Ni
2024-11-07 15:39 ` Peter Maydell
2024-11-08 14:47 ` Jonathan Cameron
2024-11-08 14:47 ` Jonathan Cameron via
2024-11-01 13:39 ` [PATCH qemu 09/10] hw/cxl: Ensure there is enough data for the header in cmd_ccls_set_lsa() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:36 ` Fan Ni
2024-11-01 13:39 ` [PATCH qemu 10/10] hw/cxl: Ensure there is enough data to read the input header in cmd_get_physical_port_state() Jonathan Cameron
2024-11-01 13:39 ` Jonathan Cameron via
2024-11-05 21:37 ` Fan Ni
2024-11-01 13:45 ` [PATCH qemu 00/10] hw/cxl: Mailbox input parser hardening against invalid input Jonathan Cameron
2024-11-01 13:45 ` Jonathan Cameron via
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=ZyqHqsFQzjDaEP8w@fan \
--to=nifan.cxl@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=esifiel@gmail.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.