[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025112807-molehill-mousiness-f3a6@gregkh>
Date: Fri, 28 Nov 2025 16:40:15 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Tianchu Chen <tianchu.chen@...ux.dev>
Cc: broonie@...nel.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: ch341: fix out-of-bounds memory access in
ch341_transfer_one
On Fri, Nov 28, 2025 at 04:06:30PM +0800, Tianchu Chen wrote:
> From: Tianchu Chen <flynnnchen@...cent.com>
>
> Discovered by Atuin - Automated Vulnerability Discovery Engine.
>
> The 'len' variable is calculated as 'min(32, trans->len + 1)',
> which includes the 1-byte command header.
>
> When copying data from 'trans->tx_buf' to 'ch341->tx_buf + 1', using 'len'
> as the length is incorrect because:
>
> 1. It causes an out-of-bounds read from 'trans->tx_buf' (which has size
> 'trans->len', i.e., 'len - 1' in this context).
> 2. It can cause an out-of-bounds write to 'ch341->tx_buf' if 'len' is
> CH341_PACKET_LENGTH (32). Writing 32 bytes to ch341->tx_buf + 1
> overflows the buffer.
>
> Fix this by copying 'len - 1' bytes.
>
> Fixes: 8846739f52af ("spi: add ch341a usb2spi driver")
> Signed-off-by: Tianchu Chen <flynnnchen@...cent.com>
> ---
> drivers/spi/spi-ch341.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi-ch341.c b/drivers/spi/spi-ch341.c
> index 46bc208f2..79d2f9ab4 100644
> --- a/drivers/spi/spi-ch341.c
> +++ b/drivers/spi/spi-ch341.c
> @@ -78,7 +78,7 @@ static int ch341_transfer_one(struct spi_controller *host,
>
> ch341->tx_buf[0] = CH341A_CMD_SPI_STREAM;
>
> - memcpy(ch341->tx_buf + 1, trans->tx_buf, len);
> + memcpy(ch341->tx_buf + 1, trans->tx_buf, len - 1);
>
> ret = usb_bulk_msg(ch341->udev, ch341->write_pipe, ch341->tx_buf, len,
> NULL, CH341_DEFAULT_TIMEOUT);
> --
> 2.39.5
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists