linux-cve-announce - CVE-2025-38671: i2c: qup: jump out of the loop in case of timeout

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: <2025082201-CVE-2025-38671-80a3@gregkh>
Date: Fri, 22 Aug 2025 18:03:08 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38671: i2c: qup: jump out of the loop in case of timeout

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

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

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

i2c: qup: jump out of the loop in case of timeout

Original logic only sets the return value but doesn't jump out of the
loop if the bus is kept active by a client. This is not expected. A
malicious or buggy i2c client can hang the kernel in this case and
should be avoided. This is observed during a long time test with a
PCA953x GPIO extender.

Fix it by changing the logic to not only sets the return value, but also
jumps out of the loop and return to the caller with -ETIMEDOUT.

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


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

	Issue introduced in 4.17 with commit fbfab1ab065879370541caf0e514987368eb41b2 and fixed in 6.1.148 with commit c523bfba46c4b4d7676fb050909533a766698ecd
	Issue introduced in 4.17 with commit fbfab1ab065879370541caf0e514987368eb41b2 and fixed in 6.6.101 with commit 0d33913fce67a93c1eb83396c3c9d6b411dcab33
	Issue introduced in 4.17 with commit fbfab1ab065879370541caf0e514987368eb41b2 and fixed in 6.12.41 with commit 42c4471b30fa203249f476dd42321cd7efb7f6a8
	Issue introduced in 4.17 with commit fbfab1ab065879370541caf0e514987368eb41b2 and fixed in 6.15.9 with commit 89459f168b78e5c801dc8b7ad037b62898bc4f57
	Issue introduced in 4.17 with commit fbfab1ab065879370541caf0e514987368eb41b2 and fixed in 6.16 with commit a7982a14b3012527a9583d12525cd0dc9f8d8934

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-38671
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/i2c/busses/i2c-qup.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/c523bfba46c4b4d7676fb050909533a766698ecd
	https://git.kernel.org/stable/c/0d33913fce67a93c1eb83396c3c9d6b411dcab33
	https://git.kernel.org/stable/c/42c4471b30fa203249f476dd42321cd7efb7f6a8
	https://git.kernel.org/stable/c/89459f168b78e5c801dc8b7ad037b62898bc4f57
	https://git.kernel.org/stable/c/a7982a14b3012527a9583d12525cd0dc9f8d8934