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.
Product status
921fc1838fb036f690b8ba52e6a6d3644b475cbb (git) before 551060efb156c50fe33799038ba8145418cfdeef
921fc1838fb036f690b8ba52e6a6d3644b475cbb (git) before bb0c58be84f907285af45657c1d4847b960a12bf
921fc1838fb036f690b8ba52e6a6d3644b475cbb (git) before 01bbf25c767219b14c3235bfa85906b8d2cb8fbc
921fc1838fb036f690b8ba52e6a6d3644b475cbb (git) before b4e002d8a7cee3b1d70efad0e222567f92a73000
5.12
Any version before 5.12
6.12.63 (semver)
6.17.13 (semver)
6.18.2 (semver)
6.19-rc1 (original_commit_for_fix)
References
git.kernel.org/...c/551060efb156c50fe33799038ba8145418cfdeef
git.kernel.org/...c/bb0c58be84f907285af45657c1d4847b960a12bf
git.kernel.org/...c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc
git.kernel.org/...c/b4e002d8a7cee3b1d70efad0e222567f92a73000
Data based on CVE®. Copyright © 1999-2025, The MITRE Corporation. All rights reserved.