linux-cve-announce - CVE-2025-68352: 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>] [day] [month] [year] [list]

Message-ID: <2025122454-CVE-2025-68352-a3fe@gregkh>
Date: Wed, 24 Dec 2025 11:34:57 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68352: spi: ch341: fix out-of-bounds memory access in ch341_transfer_one

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

spi: ch341: fix out-of-bounds memory access in ch341_transfer_one

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.

The Linux kernel CVE team has assigned CVE-2025-68352 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.11 with commit 8846739f52afa07e63395c80227dc544f54bd7b1 and fixed in 6.12.63 with commit cad6c0fd6f3c0e76a1f75df4bce3b08a13f08974
	Issue introduced in 6.11 with commit 8846739f52afa07e63395c80227dc544f54bd7b1 and fixed in 6.17.13 with commit ea1e43966cd03098fcd5f0d72e6c2901d45fa08d
	Issue introduced in 6.11 with commit 8846739f52afa07e63395c80227dc544f54bd7b1 and fixed in 6.18.2 with commit 81841da1f30f66a850cc8796d99ba330aad9d696
	Issue introduced in 6.11 with commit 8846739f52afa07e63395c80227dc544f54bd7b1 and fixed in 6.19-rc1 with commit 545d1287e40a55242f6ab68bcc1ba3b74088b1bc

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-68352
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/spi/spi-ch341.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/cad6c0fd6f3c0e76a1f75df4bce3b08a13f08974
	https://git.kernel.org/stable/c/ea1e43966cd03098fcd5f0d72e6c2901d45fa08d
	https://git.kernel.org/stable/c/81841da1f30f66a850cc8796d99ba330aad9d696
	https://git.kernel.org/stable/c/545d1287e40a55242f6ab68bcc1ba3b74088b1bc