linux-cve-announce - CVE-2025-68746: spi: tegra210-quad: Fix timeout handling

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: <2025122416-CVE-2025-68746-bd3e@gregkh>
Date: Wed, 24 Dec 2025 13:10:22 +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-68746: spi: tegra210-quad: Fix timeout handling

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

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

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

spi: tegra210-quad: Fix timeout handling

When the CPU that the QSPI interrupt handler runs on (typically CPU 0)
is excessively busy, it can lead to rare cases of the IRQ thread not
running before the transfer timeout is reached.

While handling the timeouts, any pending transfers are cleaned up and
the message that they correspond to is marked as failed, which leaves
the curr_xfer field pointing at stale memory.

To avoid this, clear curr_xfer to NULL upon timeout and check for this
condition when the IRQ thread is finally run.

While at it, also make sure to clear interrupts on failure so that new
interrupts can be run.

A better, more involved, fix would move the interrupt clearing into a
hard IRQ handler. Ideally we would also want to signal that the IRQ
thread no longer needs to be run after the timeout is hit to avoid the
extra check for a valid transfer.

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

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

	Issue introduced in 5.12 with commit 921fc1838fb036f690b8ba52e6a6d3644b475cbb and fixed in 6.12.63 with commit 551060efb156c50fe33799038ba8145418cfdeef
	Issue introduced in 5.12 with commit 921fc1838fb036f690b8ba52e6a6d3644b475cbb and fixed in 6.17.13 with commit bb0c58be84f907285af45657c1d4847b960a12bf
	Issue introduced in 5.12 with commit 921fc1838fb036f690b8ba52e6a6d3644b475cbb and fixed in 6.18.2 with commit 01bbf25c767219b14c3235bfa85906b8d2cb8fbc
	Issue introduced in 5.12 with commit 921fc1838fb036f690b8ba52e6a6d3644b475cbb and fixed in 6.19-rc1 with commit b4e002d8a7cee3b1d70efad0e222567f92a73000

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-68746
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-tegra210-quad.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/551060efb156c50fe33799038ba8145418cfdeef
	https://git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf
	https://git.kernel.org/stable/c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc
	https://git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000