CVE-2025-68746: spi: tegra210-quad: Fix timeout handling
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 currxfer field pointing at stale memory.
To avoid this, clear currxfer 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68746?
CVE-2025-68746 is categorized as a low severity vulnerability due to the rare occurrence of its impact.
How do I fix CVE-2025-68746?
Fix CVE-2025-68746 by updating the Linux kernel to the latest stable version that includes the needed patches.
What is the impact of CVE-2025-68746?
The impact of CVE-2025-68746 involves potential timeout issues when handling QSPI interrupts on busy CPUs.
Which software versions are affected by CVE-2025-68746?
CVE-2025-68746 affects specific versions of the Linux kernel that handle QSPI communications.
When was CVE-2025-68746 reported?
CVE-2025-68746 was reported following the identification of a flaw in the Linux kernel's QSPI interrupt handling.