linux-kernel - Re: [PATCH] spi: ch341: fix out-of-bounds memory access in ch341_transfer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176435290978.114164.11348727837075094329.b4-ty@kernel.org>
Date: Fri, 28 Nov 2025 18:01:49 +0000
From: Mark Brown <broonie@...nel.org>
To: Tianchu Chen <tianchu.chen@...ux.dev>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 gregkh@...uxfoundation.org
Subject: Re: [PATCH] spi: ch341: fix out-of-bounds memory access in
 ch341_transfer_one

On Fri, 28 Nov 2025 16:06:30 +0800, Tianchu Chen wrote:
> 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:
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: ch341: fix out-of-bounds memory access in ch341_transfer_one
      commit: 545d1287e40a55242f6ab68bcc1ba3b74088b1bc

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark